52223 - Mozilla is freezing a LOT lately

Status: VERIFIED FIXED

(Core :: Networking: Cache, defect, P3)

Description

[Jason Eager]

The above url doesn't directly crash mozilla, but visiting a few pages
on that site causes mozilla to hang endlessly while trying to load
a page. The task manager reports that "Mozilla has stopped responding
to the system".

Comment 1

[Asa Dotzler [:asa]]

hmm, unable to reproduce this hang.  Is it on a particular page in the site or a
particular order of laoding pages?

Comment 2

[Jason Eager]

Ok, it's not page specific. This just started happening yesterday afternoon with
build 20000910??. After loading about 8 pages, the browser will just hang. It
won't respond to any UI events (mouse over toolbar buttons for example), and
when I try to close it, Win2000 says "This application is not responding."

I just cleared my disk cache to see if that was the problem.

I'm going to have to revert back to an earlier build if this continues..I can't
use the browser when it freezes up on me this often.

Comment 3

[Jim Roskind]

Since the comment indicates that the "creatively named" demonstrtion URL is not 
key, I'm removing it.
This bug is too generic for me to give a dogfood-plus marking to.  Effectively 
this is *currently* a meta bug. It is akin to saying that "stability is poor."  
Please get a talkback report, or a stack trace from a crash, and enter that as a 
bug.  Without such info, this is not going to be reproducible, or focused enough 
for direct attention.

Thanks,

Jim

Comment 4

[Jason Eager]

Believe it or not, that was the first page that I saw this behaviour on
(followed the link from Slashdot). Then
my browser started hanging after about every 8 pages (both Win2000 and Linux).
That's why I marked it dogfood.

The hangs stopped once I cleared my disk cache. Obviously, this bug is a dup.

Comment 5

[Doron Rosenberg (IBM)]

--> networking cache

Comment 6

[Suresh Duddi (gone)]

Bouncing to QA in ahope that they will make this bug a more reproducible and 
more definite.

Comment 7

[Jason Eager]

No No No, this is a DUPE of something. I just can't quite remember what 
the original "our cache processing completely sucks/We corrupt everything the 
cache touches" bug was. It's obviously related to that bug. Marking "qawanted".

Comment 8

[Tom Everingham]

jce are you still seeing this?  I beleive some work was done recently to keep 
the cache from getting corrupted.

Comment 9

[gordon]

No one has seen this problem since October 2000.  Marking Fixed.

Comment 10

[Tom Everingham]

verified