486926 - after running for several days, some connections freeze and consume 100% CPU

Status: VERIFIED DUPLICATE of bug 397053

(Camino Graveyard :: General, defect)

Description

[hhaamu]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 SeaMonkey/2.0a3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.8pre) Gecko/2009022317 Camino/2.0b2

Sorry, I can't really pinpoint this bug well, so I'll just write down everything I can.


Camino has been running since 2009-03-25 (11 days). Now, some of my http connections just freeze (never complete), and camino starts consuming 100% cpu until I close the tab with the frozen connection. I can close the tab and reopen it for a new attempt (sometimes works, sometimes doesn't).

Once this connection-freeze has happened, all further connection attempts (in other tabs) fail (until I close the offending tab).

A restart of camino fixes the problem. Until I restart, it is intolerable to browse.


Alternatively, the connections do not freeze nor consume 100% cpu, but instead reset (give me the "Connection was reset" page, or display the page without CSS if the http connection for CSS was reset, etc).



I have flashblock enabled, adblock disabled.

My network changes occasionally (via OSX's "Location" menu): Automatic (vanilla network setup), and a custom DNS server + proxy (more accurately, privoxy + squid3). During the eleven days camino has been running, I have changed back and forth maybe four times.

The bug, once it appears, happens both without proxy and with proxy.

Reproducible: Sometimes




I take an example of the behaviour on the page http://garfieldminusgarfield.net/ on proxy setup. The proxy has cached everything except the newest comic strip.

- the images takes a while to load, and never load fully (about 70% completion)
- consumes 100% of one cpu core
- statusbar says "Connected to www.projectwonderful.com" (external javascript)

Comment 1

[hhaamu]

Attachment: Activity Monitor sample

Comment 2

[hhaamu]

Based on sample, this might be bug 429304

Comment 3

[Chris Lawson (gone)]

Have you tried making a custom build with the patch on bug 429304 incorporated to see if that fixes the problem?

Comment 4

[hhaamu]

another freeze: Apr05->today => ~8 days


I now patched myself with wip6 (attachment 316339 [details] [diff] [review]) from the bug:
Version 2.0b3pre (1.9.0.10pre 2009041320)

I guess I'll have to wait for a week or two for possible reproducing...

Comment 5

[hhaamu]

Nope -- Camino just hit the "don't want to load CSS" stage (no excessive CPU usage (yet?)). Links opened in new tabs don't want to load (just blank: no error message, no URL in location bar).

Last time I used the proxy was two or three days ago.

One more thing worth of mention: The majority of my tabs don't get a history longer than 1 page. I heavily use my middle mouse button.

Comment 6

[Chris Lawson (gone)]

(In reply to comment #5)

> One more thing worth of mention: The majority of my tabs don't get a history
> longer than 1 page. I heavily use my middle mouse button.

The two things are very likely related; links opened in a new tab will not have any history, since they're being opened in a new tab (which is exactly what you'd expect to happen).

cl

Comment 7

[hhaamu]

Eh, yes, I do know about history getting wiped on tab-open (isn't that another bug?), but does it relate to this bug?

Comment 8

[Chris Lawson (gone)]

(In reply to comment #7)
> Eh, yes, I do know about history getting wiped on tab-open (isn't that another
> bug?), but does it relate to this bug?

It's not a bug, period. A new tab doesn't have any history at all, so you shouldn't be seeing anything in the session history for a new tab.

Comment 9

[hhaamu]

OK, now I'm fairly sure that the patch bug 429304 fixed half of the problem (100% CPU usage), but there's still the odd connections freezing issue (it's not "connection reset by peer" anymore, but just... never being made).

I also observed a... uh, "dead link" behaviour. Links just stop working. When I click on them, the tab title very briefly changes to the "Loading" state. If I middle-click on dead links, they bring the earlier-mentioned empty tab. Even the urlbar doesn't respond when pressing enter. Closing the tab and opening a new one helps. This doesn't happen always, but it usually does after clicking a few links on a page.

I can confirm from my proxy logs that e.g. on one page, only nine HTTP requests are made/completed (there _should_ be about ten to twenty image requests). The breakdown is as follows:
1. main HTML page
2. favicon
3-7. five external images (of which only four are rendered?)
8. external javascript
9. external javascript
by "external" I mean something not located on the same host as the originating html.


For the example of garfieldminusgarfield, no images are loaded, unless I cmd-R which causes the latest and (if I'm lucky) the second-to-latest comic to load.


One more "abnormal" config I have is disk cache disabled. Memory cache is on.

Comment 10

[Stuart Morgan]

From irc debugging: this turned out to be an older version of Flash, and our old friend the Flash file descriptor leak.

Comment 11

[Chris Lawson (gone)]

Yay for leaking file descriptors...