Latest bitHopper, and the one without burps patch, stops functioning normally after a while on my box.
First it starts with these timeouts http://pastebin.com/WZn6jpRh
Then i see this errors: http://pastebin.com/rbgSBRMs
After a while it is full of these errrors: http://pastebin.com/WYp1N3KV
And I see a lot of SYN_SENT connections: http://pastebin.com/EQmWs2EV
Screenshot of web interface in the state of "User timeout caused connection failure": http://imageshack.us/photo/my-images/4/80919683.png/
Screenshot after restart: http://imageshack.us/photo/my-images/143/ss2pj.png/

After investigation I come to conclusion that arsbitcoins block/rate limit tcp connections and bitHopper tries to open new connections to the host until it runs out of free sockets. Disabling arsbitcoins helps, but I think there should be a better way for bitHopper to handle TCP timeouts/SYN-packets dropped by pools. I am not sure if http/1.1 keep-alive is implemented. But it could help to reduce stressing pools with huge load of new tcp connections.