Closed
Bug 323262
Opened 19 years ago
Closed 19 years ago
crash on exit after reloading a page
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: ajschult784, Assigned: darin.moz)
References
()
Details
(Keywords: crash, regression)
Attachments
(1 file)
2.65 KB,
text/plain
|
Details |
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).
Reporter | ||
Comment 1•19 years ago
|
||
Assignee | ||
Comment 2•19 years ago
|
||
Are you able to reproduce this using FF?
Updated•19 years ago
|
Summary: crash on exit after reloading a pgae → crash on exit after reloading a page
Reporter | ||
Comment 3•19 years ago
|
||
I crashed with a CVS trunk firefox build from Jan 6
Reporter | ||
Comment 4•19 years ago
|
||
backing out "Bug 316414 part 1, try #2" fixes the crash for me
Blocks: 316414
Reporter | ||
Comment 5•19 years ago
|
||
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?
Reporter | ||
Comment 6•19 years ago
|
||
This stopped happening with linux seamonkey trunk build 2006051109, so bug 326273 fixed it
Status: NEW → RESOLVED
Closed: 19 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.
Description
•