Closed
Bug 77842
Opened 23 years ago
Closed 23 years ago
timer / presshell crash in mailnews
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: sspitzer, Assigned: sspitzer)
Details
I crashed in mailnews. some sort of timer / presshell crash deref a null comptr. cc'ing hyatt. he mentioned something about a scary time, before we paint that he's got 2 pres shells. could this be fallout? NTDLL! 77f9f9df() nsDebug::Assertion(const char * 0x0298bbb4 `string', const char * 0x0298bbf8 `string', const char * 0x029915e8 `string', int 652) line 286 + 13 bytes nsDebug::PreCondition(const char * 0x0298bbb4 `string', const char * 0x0298bbf8 `string', const char * 0x029915e8 `string', int 652) line 430 + 21 bytes nsCOMPtr<nsIScriptGlobalObject>::operator->() line 652 + 34 bytes PresShell::FireResizeEvent() line 2799 + 32 bytes PresShell::sResizeEventCallback(nsITimer * 0x05254b20, void * 0x05264900) line 2785 nsTimer::Fire() line 194 + 17 bytes nsTimerManager::FireNextReadyTimer(nsTimerManager * const 0x02013a80, unsigned int 0) line 117 nsAppShell::Run(nsAppShell * const 0x005444b0) line 118 nsAppShellService::Run(nsAppShellService * const 0x00544910) line 408 main1(int 2, char * * 0x004841d0, nsISupports * 0x00000000) line 1005 + 32 bytes main(int 2, char * * 0x004841d0) line 1300 + 37 bytes mainCRTStartup() line 338 + 17 bytes KERNEL32! 77e87903()
This sounds bad, but would need some steps to reproduce and/or verify when fixed.
Comment 2•23 years ago
|
||
seth, I have this fixed with the patch to 76495.
Assignee | ||
Comment 3•23 years ago
|
||
hyatt is my hero! *** This bug has been marked as a duplicate of 76495 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup, if you look at bug 76495, it was verified fixed by jrgm, and I tried the steps in that bug, and it didn't crash with 2001-05-18 on Windows 2000.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•