itix: I think Hooligan's issue is different. At least how we tried to debug it long time ago. There wasn't any visible issue causing the stalls on him IIRC. But the thing you're talking with Iltalehti is because some ad server doesn't respond or stalls for some other reason. You can see it on the Network Activity window that it's waiting for some url. You can get Iltalehti quick if you deny http://atemda.com/* in Content Blocking. On Hooligan's case there wasn't anything waiting in Network Activity window...

And that atemda.com for example could be an issue of some feature lacking in fragmented tcp packet handling in NetStack, I'd guess.

[ Edited by jPV 09.01.2013 - 13:31 ]