User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4 After browsing for a long time, page elements on various sites (YouTube, DeviantArt, and more) stop loading. The pages load incomplete. Shift-reload sometimes forces a complete reload, sometimes not. The failure can be subtle, and seems to get worse as time goes on. This behavior continues until Firefox is restarted, so I suspect some resource is running out and leading to the incomplete loads. This is difficult to reproduce, and I don't know of any reliable way of doing so. It just comes up after lots of browsing in lots of tabs. Reproducible: Sometimes Steps to Reproduce: 1. Just browse the web heavily for a few hours. Actual Results: Pages eventually start loading incomplete. Expected Results: Pages should load completely no matter how long Firefox has been open.

The problem just happened again, only this time Firefox crashed shortly after it occurred. Crashreporter came up and I tried to submit the report, but I'm not sure it made it. The crash report mentions this bug, so if you receive it, you'll know which one it is. I'll try to collect more information on what is causing this problem. I doubt it is hardware-related as it has happened on *both* of my Macs so far.

This log entry was logged just before this problem hit my Firefox 3b4 session again: 3/31/08 3/31, 8:38:11 PM firefox-bin[406] *** Assertion failure in -[NSMenuItem initWithTitle:action:keyEquivalent:], /SourceCache/AppKit/AppKit-949.27/Menus.subproj/NSMenuItem.m:182 3/31/08 3/31, 8:38:11 PM firefox-bin[406] NSInternalInconsistencyException: Invalid parameter not satisfying: aString != nil CrashReporter also crashed while submitting the bug report. This is bizarre.

I just wanted to note that this problem is still happening with the latest Firefox 3 release (RC2) on Mac OS 10.5.3.

Still happening in RC3. And it seems worse than before. It used to be if I avoided abcnews.com, then the problem wouldn't happen. Now it just seems to happen after about 2 hours of browsing.

James, I'm glad to see I'm not the only one seeing this. I've been wondering why this serious problem hasn't received more attention, and looking for ways to bump it up the ladder. Release day is right around the corner; hopefully widespread usage will expose the problem more and get it attacked and fixed.

My suspicion is that there may be some sort of conflict with an add-on that is exacerbating the problem - otherwise, we should have more reports of this. I created a new profile and have only added in FoxMarks (because I need my bookmarks). At the rate RC3 has been giving me problems, I should know within a day of throwing out the other Add-Ons helps. As I noted, it used to be that abcnews.com triggered this problem for me with FF 2.0.0.x. Now, it's some combination of everything else....

The only add-on I have installed is FlashBlock, and that's one that I consider absolutely critical to browsing. It'd be sad if that were the add-on causing the problem. I suppose I could brave the rapids and turn off Flashblock for a few days. We'll see how that goes. Flashblock has, historically, never caused any problems. I guess there's a first time for everything. :(

Type about:config in the address bar and look for these values: network.http.max-connections network.http.max-connections-per-server Set them to something higher like 100 and 10 respectively and restart Firefox. I assume the problem is the sites use up all of Firefox's connections so other pages won't load.

(In reply to comment #8) > Set them to something higher like 100 and 10 respectively and restart Firefox. > I assume the problem is the sites use up all of Firefox's connections so other > pages won't load. I very much doubt this is the case. The problem manifests as not just pages failing to load, but UI elements no longer working. For instance, the last time this happened, I couldn't open Tools -> Add-ons, nor could I quit with the "Quit" in the Firefox/File menu. I disabled all plugins at this point and am going to try to reproduce the problem.. If it happens again, I'll try your suggestion, but it's doubtful.

I already had these set up to 60 and 15, but I tend to feel the same way as John Flynn - pages not loading is one thing, but the UI going completely out to lunch is something else. When this happens to me, nothing on the menus works. John, regarding FlashBlock - that's actually a prime suspect of mine. FlashBlock has had crashing issues with 2.0.0.x for me so for the purpose of trying to narrow down this issue, I'm running without it for now....

I am having this problem too, both in Firefox 2, and al 3 beta's and release candidates on Mac OS X 10.4, also with the FlashBlock plugin installed. After a while pages fail to load properly, most notably the images not appearing and the stylesheets not being loaded. After this the menu's stop working and only using "Force Quit" will terminate the application.

I've encountered the bug in FF2 and FF1 as well. I'm notorious for keeping browsing sessions going until I'm absolutely forced to restart. The problem occurred much more often in FF1 than FF2 for me. A dozen windows with a dozen tabs each is light surfing for me. When the problem occurs as it did this past weekend in FF 2.0.0.14 no new windows can be opened. No pages can be reloaded. No new sites can be loaded in existing windows. The Back and Forward buttons stop working. Everything grinds to a halt essentially. The problem was so severe this weekend that killing FF, restarting it and letting Session Saver recover the last session failed to work correctly. The browser would crash while loading some of the pages. Subsequent Session Saver recoveries would result in windows with dozens of empty tabs (the windows that hadn't fully loaded prior to the previous crash).

Okay, I have been browsing for several days with Flashblock off, painful as it may be. There has been no weirdness during this time, so I suspect the cause of this problem is indeed Flashblock. It must be some sort of interaction between Flashblock and FF3, because I've never had this problem before on FF2 or prior versions. I've switched to Adblock instead, which accomplishes the same thing, though it's a bit more extreme. I don't mind seeing ads; it's just the animated, crazy CPU hogging flash ones that I want to get rid of. I'd rather support advertisers that DON'T use flash ads, but until Flashblock is fixed, I'm going to have to settle with blocking them all. I filed a comment under a very similar bug in the Flashblock Bugzilla; hopefully it'll get looked at. There seems to be instability issues with Flashblock in general with FF3; CNN video suddenly started working again when I disabled it.

My experiments seem to agree - and also appear to suggest that Flashblock needs to be completely uninstalled in order for it not to cause problems. On two systems where I was able to reproduce the systems, one continued to have Firefox crash until I completely uninstalled Flashblock.

As I reported earlier I had this problem with many versions of Firefox and FlashBlock on Mac OS X. One month ago I switched from Firefox 3.0 to Minefield, an optimized build for Mac OS X to get increased performance. I have not noticed much improvement in speed, but have not had a single problem with incomplete page loads ever since, even with dozens tabs containing Flash video spread out over several windows. With Firefox this happened at least once a day. Minefield with Flashblock and all other extensions continue to work fine. Minefield can be downloaded at the following location, maybe someone else who is having the same problems can try it out and report their experiences? http://www.beatnikpad.com/archives/2008/07/16/firefox

I can confirm this bug on with 3.01 on Mac OS X 10.4.11. I also notice that once it's in this state where pages don't load/render correctly, quitting doesn't work anymore via the menu item or Command+Q. I have to force quit.

I wanted to add to this that I have experienced this bug as well. However, it seems to come and go with different releases of either firefox or flashblock. I have not confirmed that disabling flashblock on mine resolves it but I am experiencing the same symptoms and have only that add-on installed so I imagine it would. It seems that when firefox 3 first came out I had this problem a lot. Later the problem went away with upgrades. However a few weeks ago I believe firefox and flashblock both had updates released and after those updates the problem has returned. It is very frustrating especially when a force quit is required as then I lose all of the tabs that I have opened. In the meantime I guess I will uninstall flashblock and find an alternative but I hope that this does become a confirmed bug and given some more attention. Thanks.

Same problem here, with FireFox 3, on a PowerBook (G4) running Tiger. After a while (typically a few hours), pages render incomplete, CSS is not loaded, images are missing. Sometimes reload fix it, sometimes not. It happens very often on facebook. Sometimes I can quit via the menu, sometimes the menu does not do anything (ie: Quit does not quit) and I have to Force Quit FireFox. No crash report is being generated. When that happens, the "Greasemonkey" scripts are not executed either. Note that contrary to others, I do not have the FlashBlock plugin. I do have the AdBlock plus, however.

xref bug 402371 Are you on a consumer grade network router/switch at home? Can you reproduce with the latest v3.1 beta? http://www.mozilla.com/en-US/firefox/all-beta.html (backup your profile first)

Note: I'm the reporter of bug 402371 (which is basically the same bug IMHO). And since Flashblock is mentioned here: I also use Flashblock. (Note that I also use Flashblock on my Linux machines, but I've never seen this problem on them.) I wonder whether the fact that some contents like Flash are blocked has the effect of (randomly?) filling some resources, leading to random problems after a while when loading other contents.

Hmmm... in bug 430941 #13, a user said that he noticed the problem with no extensions.

no response to comment 19, so => incomplete