Try www.cnn.com. Wait for the page refresh time (30 minutes). The page apparently is refreshed, but embedded pictures won't load. Switching to another web site results in endless wait for the page data. The browser http requests now are completely halted. Opening another browser window and requesting another site won't work. Only cure is to shut down and restart. Have to admit that I cannot prove it is the page refresh that causes this bug, but since running this release, that bug showed off five times (in two days), and personal bug tracking boils down to this verdict. Apart of this, this release is close to perfect! Please hold on! Regards from Berlin

In your privacy settings have you enabled load images from the originating server only? This site uses images from many servers.

No, image loading is unrestricted. I checked that feature (load from original server only) before, but wasn't using it that time. Anyway, that should not cause the other related errors: opening another browser window and requesting a text only site is blocked, too (after the incident). If no one else is experiencing these problems (they are quite obvious to me), perhaps it is related to the open mail window (using IMAP)? Although that one still was functional. Regards

->networking for a look.

I'm seeing the same behavior since going to 0.9.3. What's interesting is that this problem bites me at home (DSL connection with a Linux box doing NAT for my desktop machine), while at work, I have no problems. Can't see any differences in Mozilla configuration between home and work. Very curious indeed...

Yes, I am NATing too (on a separate firewall in the network). Let me give you an exact setup to reproduce the problem: Open one browser window with www.cnn.com. Open another one with www.slashdot.org. Open mail window with imap, message fetching cycle 1 minute. The first page refresh of www.cnn.com (after 30 min) is OK. The second page refresh (after 60 min) appears slower for the images. The third refresh (after 90 min) hangs for the images. No further browsing activity possible, email still operational. No other activity during the test cycle.

Sorry, forgot that: Our network here is doing NAT (on a linux 2.2 kernel) as noted before, but mozilla won't know, as all HTTP traffic goes through squid v2.2, on a separate linux box. Yes, that machine is setup in the proxy settings of mozilla. And, yes, squid is running flawlessly with mozilla 0.6, konqueror and the like.

Some additional info: I came in to work this morning, and found my Mozilla window with cnn.com wedged just like I always experience at home. Since I sincerely doubt Red Hat moved over to NAT last night while nobody was looking, it seems that the bug is not tickled explicity *by* NAT, but rather by some other characteristic that is normally exhibited by NAT, but can also appear in other network configurations. I normally keep three Mozilla windows open and, as before, the other two windows continue to operate normally. If anyone has suggestions as to how I might be able to collect more information on this problem, I'd be happy to help narrow down the cause...

I'm seeing something simmilar. See my comment in bug 95499

+qawanted - bbaetz: any ideas?

Possibly a dupe, but marking NEW for now since it has been confirmed by Ed Bailey.

It seems to be fixed now, reporter please try this with new trunk builds.

Well, CNN changed their site so drastically that 0.9.3 has been working perfectly on www.cnn.com. So if you're using only that site as an indicator of whether the bug still exist, I don't think it's possible to say conclusively that the bug has been resolved.

I think that this bug was only another incarnation of the bu 95499. With Mozilla 0.9.3 and trunk builds from that time I've frequently got the Mozilla to the state when the network subsystem locked and stopped to issue new connections. It was fixed sometime before 0.9.4. I've tried another pages with automatic refresh and they work fine with current builds. So because there isn't (won't be) any real testcase for this bug it should be resolved as INVALID.

I am using mozilla 0.9.4 since a couple of days (the linux build only). To me, it appears as if the bug has disappeared, but I will check it again this evening (european time) on an external site issuing page refreshs. As far as I can see, CNN works fine, but at times like these, it is unusual that I stay tuned to one (news) site for a long time without further operation. The network collapse needed some 2 to 3 consecutive page refreshs. I will now set up a test case. Sorry that I didn't find the time the days before, but, you know the problem, I am a software developer under some pressure from other issues :-) Thanks for your great work! Release 0.9.4 became my primary browser now, before, I always fell back to 0.6.x after some days. (it was me reporting this bug initially)