[Interest] Strange QWebSocket/QTcpServer interaction... Bug in Firefox?

Guido Seifert wargand at gmx.de
Sun Dec 21 22:41:34 CET 2014

> Why is it a memory leak?

When I get a socket from QTcpServer... who is responsible for its deletion?
Since I never expected to get such dead connections, I did not handle them
correctly. I deleted them after I got data.
> If you're implementing an HTTP server, close TCP connections that didn't send 
> any requests within a reasonable amount of time.

Sure, that's what I do now. It still is a strange behaviour and hardly to be
explained with: 

> Browsers can (and do) pre-emptively connect to servers if they think they
> might need to talk to them.

For me this is a useless overhead.

And I just got confirmation: The android 5 browser is also NOT doing this. Up to 
now it is only the Firefox.


More information about the Interest mailing list