All users were logged out of Bugzilla on October 13th, 2018
On the nightly with build ID 2000041205, you only need to load a small number of websites before this becomes really evident. Mozilla isn't properly closing its network connections. Once enough are open, you get a TCP - Not enough memory error. netstat gives a whole lot of lines like the following: TCP (my hostname:port) (remote address:80) CLOSE_WAIT After exitting Mozilla, all the connections will disappear from the netstat listing.
As a followup to this, the number of still active connections balloons much faster in the original window than in any new windows, although it will still slowly increase as you browse in them. I don't think it's relevent, but the TCP Error: Not enough memory only comes up once there are 93 network connections.
This remembers me of bug 35150, but that is marked fixed 4/11. Maybe this fix has something to do with this...
Actually it will keep up to keep-alive.max-connections (default is 30) open connections in the keep-alive queue. So, it's normal (there was a leak before which was fixed).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
verified, since today's 10am build no longer has the problem.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.