Closed
Bug 124365
Opened 24 years ago
Closed 23 years ago
Mozilla crashes if you restart quickly after shutting down
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 119034
People
(Reporter: raj, Assigned: asa)
Details
(Keywords: crash)
Mozilla 0.9.8 milestone (2002-02-04-06), Windows 2000 Pro SP2.
If you shut down Mozilla compeletly (including turbo) and then restart it
immediately (within a few seconds) then it gives you an application error about
being "unable to write to memory" or something before crashing and giving a
Talkback window.
Reproducibility: always.
Steps to reproduce:
1) Start Mozilla
2) Shut down Mozilla completely (including turbo mode)
3) Restart Mozilla quickly, eg by using a shortcut on your desktop, within a few
seconds.
Expected result: Mozilla loads normally
Actual result: Mozilla crashes with a Windows error message and gives a Talkback
result
I'm not sure which component to put this into, so I'll leave it in
Browser-General until someone can decide where it goes. To be honest, I'm sure
that this must have been reported before, but my searches haven't picked
anything up and I guess that it's better to have too many bug reports, than too
little :o).
Comment 1•24 years ago
|
||
Reporter: Please set severity level to "critical", and add the keyword "crash".
Comment 2•24 years ago
|
||
WFM 2002020703/WinNT4
Reporter: Talkback should catch most crashes and offer to send in a crash
report. Developers can retrieve that crash report and attach it to your bug
report if you provide either the Incident ID (you can get it by running the
talkback program from /components/talkback/). Thanks for your help in testing
Mozilla and reporting bugs.
| Reporter | ||
Comment 3•24 years ago
|
||
Some talkback IDs are: TB2666276X, TB2666251E, TB2525618G
Raj.
Comment 4•23 years ago
|
||
CC: stephend@netscape.com, for talkback retrieval, please (TB2666276X,
TB2666251E, TB2525618G)
0x002f5b8b
NS_GetGlobalComponentManager
[d:\builds\seamonkey\mozilla\xpcom\components\nsComponentManager.cpp, line 3323]
nsComponentManager::CreateInstance
[d:\builds\seamonkey\mozilla\xpcom\components\nsComponentManagerObsolete.cpp,
line 101]
nsNativeAppSupportWin::GetCmdLineArgs
[d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsNativeAppSupportWin.cpp, line 1599]
nsNativeAppSupportWin::HandleRequest
[d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsNativeAppSupportWin.cpp, line 1328]
MessageWindow::WindowProc
[d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsNativeAppSupportWin.cpp, line 818]
USER32.DLL + 0x1b60 (0x77e11b60)
USER32.DLL + 0x2f29 (0x77e12f29)
USER32.DLL + 0x7b92 (0x77e17b92)
ntdll.dll + 0x2032f (0x77fa032f)
USER32.DLL + 0x2ca2 (0x77e12ca2)
ole32.dll + 0x4cf5d (0x77a9cf5d)
ole32.dll + 0x4cdbd (0x77a9cdbd)
ole32.dll + 0x1583c (0x77a6583c)
ole32.dll + 0x156eb (0x77a656eb)
0xffffffff
Comment 6•23 years ago
|
||
*** This bug has been marked as a duplicate of 119034 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•