Closed
Bug 280341
Opened 20 years ago
Closed 20 years ago
crash at startup [@ nsCOMArray_base::~nsCOMArray_base]
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tobias, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050129 Mnenhy/0.7.0.10002
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050129 Mnenhy/0.7.0.10002
Seamonkey-Trunk-Zip-Builds since 2005012822 first seen, but also with 2005012900
(Tinderbox/Creature) and now 2005012905-Nightly are crashing sometimes at startup.
Reproducible: Sometimes
Steps to Reproduce:
1. Get an current Trunk-Nightly, using *.zip-Builds here.
2. Unzip
3. Start Mozilla
Actual Results:
First two Startups Mozilla crashes, third time Mozilla will start properly.
Expected Results:
No crash at Startup.
Got some Talkback Incidents: TB3366522Q, TB3366515Z, TB3366512W
Note, the 2005012905-Build has started up at first try well, but after killing
Mozilla via Taskmanager for killing Popups from Bug 280326 Mozilla crashes at
next Startup.
And additional, I have got two Profiles, Profilemanager gets up ervery time
properly, crash occours whlie start the selected Profile.
Comment 1•20 years ago
|
||
0x003d3901
nsCOMArray_base::~nsCOMArray_base
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/ds/nsCOMArray.cpp,
line 61]
nsXULPrototypeCache::GetPrototype
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/content/xul/document/src/nsXULPrototypeCache.cpp,
line 273]
nsChromeProtocolHandler::NewChannel
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/rdf/chrome/src/nsChromeProtocolHandler.cpp,
line 677]
nsIOService::NewChannelFromURI
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsIOService.cpp,
line 481]
NS_NewChannel [../../dist/include/necko/nsNetUtil.h, line 170]
nsDocShell::DoURILoad
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 5677]
nsDocShell::InternalLoad
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 5598]
nsDocShell::LoadURI
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 764]
nsWindowWatcher::OpenWindowJS
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 771]
nsWindowWatcher::OpenWindow
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 458]
nsAppStartup::OpenWindow
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 788]
nsAppStartup::LaunchTask
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 726]
nsAppStartup::CreateStartupState
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 610]
DoCommandLines
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 756]
main1
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1272]
main
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1811]
WinMain
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1839]
KERNEL32.DLL + 0x2893d (0x77e9893d)
Updated•20 years ago
|
Summary: crash at startup [@nsCOMArray.cpp] → crash at startup [@ nsCOMArray_base::~nsCOMArray_base]
Similar results using Build 2005013005 with mozilla-win32-installer.exe under
Windows ME. Crashed on startup from the install process.
Talkback ID is TB3385472E
there's more going on too: See what happens to your CPU if you start moz, open
"about mozilla" - close about mozilla, and then quit mozilla. I almosto fried my
laptop.
I reported this as a blocker in bug 280427
Comment 4•20 years ago
|
||
Bug 280341 was backed out. Do you still see the crash?
Comment 5•20 years ago
|
||
hmm, bug 278443, not 280341
Reporter | ||
Comment 6•20 years ago
|
||
Have tried to crash the new Build 2005013109 (Creature-Tinderbox) first with
backed out Bug 278443 and no crash occours. Runs well and stable again.
Todays 2005013106 was crashing reproduceable, deleting the compreg.dat before
startup crashes the Build for sure. 2005013109 startsup fine withe previous
deleted compreg.dat.
And hinting again, think this crash has to do something with starting Mozilla
here always with the Profilemanager, I cant reproduce this crash with another
Installation where only one profile exist.
Also I can't reproduce Bug 280456 anymore with the new Build, think this was
fixed too.
Reporter | ||
Comment 7•20 years ago
|
||
Have tested with some more Builds and I can't reproduce this anymore after Patch
from Bug 278443 was backed out.
Mark this as resolved=worksforme, hope thats the right solution.
Add keywords regression and crash.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Keywords: crash,
regression
Resolution: --- → WORKSFORME
Comment 8•20 years ago
|
||
Reopen based on experienced crash - TB3421283X (Seamonkey-trunk/2005013106/W2K):
nsCOMArray_base::~nsCOMArray_base
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/ds/nsCOMArray.cpp,
line 61]
nsXULPrototypeCache::GetPrototype
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/content/xul/document/src/nsXULPrototypeCache.cpp,
line 273]
nsChromeProtocolHandler::NewChannel
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/rdf/chrome/src/nsChromeProtocolHandler.cpp,
line 677]
nsIOService::NewChannelFromURI
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsIOService.cpp,
line 481]
NS_NewChannel [../../dist/include/necko/nsNetUtil.h, line 170]
nsDocShell::DoURILoad
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 5725]
nsDocShell::InternalLoad
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 5638]
nsDocShell::LoadURI
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/docshell/base/nsDocShell.cpp,
line 765]
nsWindowWatcher::OpenWindowJS
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 771]
nsWindowWatcher::OpenWindow
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp,
line 458]
nsAppStartup::OpenWindow
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 788]
nsAppStartup::LaunchTask
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 726]
nsAppStartup::CreateStartupState
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 610]
DoCommandLines
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 756]
main1
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1272]
main
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1811]
WinMain
[c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1839]
kernel32.dll + 0x16d4f (0x7c816d4f)
There are other crashes from this year's builds:
http://tinyurl.com/3n2cd
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 9•20 years ago
|
||
(In reply to comment #8)
> Reopen based on experienced crash - TB3421283X (Seamonkey-trunk/2005013106/W2K):
2005013106 is the nightly preceding the back-out, tinderbox build 2005013109 was
the first build not showing the crash in bug 280456. I assume Tobias closed this
bug based on that tinderbox build, do you still see crashes with current nightlies?
https://bugzilla.mozilla.org/show_bug.cgi?id=280456#c5
Reporter | ||
Comment 10•20 years ago
|
||
(In reply to comment #9)
> the first build not showing the crash in bug 280456. I assume Tobias closed this
> bug based on that tinderbox build, do you still see crashes with current
nightlies?
Yes, I have closed this after do some testing with the Builds with backed out
Patch for Bug 278443, first available was Tinderbox-Build 2005013109 and then
tested some Builds later. I am unable to reproduce the crash now withe the new
Builds.
The latest TB-Reports are from Build 2005013106, which was still brocken.
Because that I think we can close this one here, but I am a little unsure if the
right solution was "Fixed" or "Worksforme" because there was not a real Patch
for this Bug. Adam, feel free to set the right solution.
Comment 11•20 years ago
|
||
Based upon comment 10, closing as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
QA Contact: general → irixman+bugzilla
Resolution: --- → WORKSFORME
Updated•14 years ago
|
Crash Signature: [@ nsCOMArray_base::~nsCOMArray_base]
You need to log in
before you can comment on or make changes to this bug.
Description
•