Closed Bug 153763 Opened 23 years ago Closed 18 years ago

crash quiting viewer [@nsAppShellService::HandleExitEvent]

Categories

(Core Graveyard :: Viewer App, defect, P3)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: timeless, Assigned: dcone)

Details

(Keywords: crash)

Crash Data

cvs opt profile trunk build from this weekend nsAppShellService::HandleExitEvent(PLEvent * 0x025454f8) line 560 + 11 bytes PL_HandleEvent(PLEvent * 0x025454f8) line 597 PL_ProcessPendingEvents(PLEventQueue * 0x00263527) line 526 + 6 bytes _md_EventReceiverProc(HWND__ * 0x0011f458, unsigned int 2147348480, unsigned int 4279001, long 2) line 1078 main(int 2, char * * 0x00432ed8) line 158 + 7 bytes VIEWER! mainCRTStartup + 227 bytes KERNEL32! 77e8d326() - aEvent 0x025454f8 |+ link {...} | handler 0x02a674b5 nsAppShellService::HandleExitEvent(PLEvent *) | destructor 0x02a674d7 nsAppShellService::DestroyExitEvent(PLEvent *) | owner 0x00000000 | synchronousResult 0x00000000 | lock 0x0247de58 | condVar 0x02463a30 \ handled 0 void* PR_CALLBACK nsAppShellService::HandleExitEvent(PLEvent* aEvent) { ExitEvent* event = NS_REINTERPRET_CAST(ExitEvent*, aEvent); // Tell the appshell to exit event->mService->mAppShell->Exit(); // <= crash here // We're done "shutting down". // unless we are currently "starting up" in which case this event wasn't properly handled. if (!event->mService->mInProfileStartup) event->mService->mShuttingDown = PR_FALSE; return nsnull; } (ExitEvent*)aEvent CXX0019: Error: bad type cast
viewer file>&Exit works viewer chrome://global/content/console.xul file>E&xit crashes
Keywords: crash
Priority: -- → P3
Target Milestone: --- → Future
QA Contact: asa
check this out <http://lxr.mozilla.org/seamonkey/search?string=E%26xit> perhaps related? should these not be &Exit instead of E&xit?
Viewer has been CVS removed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
Crash Signature: [@nsAppShellService::HandleExitEvent]
You need to log in before you can comment on or make changes to this bug.