Closed Bug 323262 Opened 17 years ago Closed 16 years ago

crash on exit after reloading a page

Categories

(Core :: Networking: Cache, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: ajschult784, Assigned: darin.moz)

References

()

Details

(Keywords: crash, regression)

Attachments

(1 file)

With seamonkey linux trunk 2006011204, if I load http://www.mozilla.org/, reload it and then exit, I crash during shutdown in cache code after it asserts a couple times:

###!!! ASSERTION: nsCacheEntryHashTable not initialized: 'initialized', file /build/andrew/moz-debug/mozilla/netwerk/cache/src/nsCacheEntry.cpp, line 444
###!!! ASSERTION: nsCacheEntryHashTable not initialized: 'initialized', file /build/andrew/moz-debug/mozilla/netwerk/cache/src/nsCacheEntry.cpp, line 460

The crash doesn't happen for every page, but I haven't been able to make a simple testcase from the .mozilla.org page.

I'm seeing a regression between linux seamonkey trunk builds 2005113010 and 2005120101 (which seems to have nothing cache-related).
Attached file stacktrace
Are you able to reproduce this using FF?
Summary: crash on exit after reloading a pgae → crash on exit after reloading a page
I crashed with a CVS trunk firefox build from Jan 6
backing out "Bug 316414 part 1, try #2" fixes the crash for me
Blocks: 316414
Poking through talkback data showed 6 firefox users hit this on linux in January (which would make it the #2 crasher on linux).  Windows doesn't seem to crash or crashes with a different frame at the top (linux stacks in talkback have 0x00000XXX at frame 9, where XXX = 000-FFF), see TB13992829Q
Flags: blocking1.9a1?
This stopped happening with linux seamonkey trunk build 2006051109, so bug 326273 fixed it
Status: NEW → RESOLVED
Closed: 16 years ago
Depends on: nsIThreadManager
Flags: blocking1.9a1?
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.