Closed
Bug 527758
Opened 15 years ago
Closed 15 years ago
New startup crash [@ nsThreadManager::Init()] in 3.5.5
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 526586
People
(Reporter: jst, Unassigned)
Details
So far we've seen 923 crashes in 3.5.5 with the signature nsThreadManager::Init(), which is a signature we've never seen in any other 3.5 release, which means it was most likely introduced in 3.5.5. The stacks seem to all look like the one in this crash report
http://crash-stats.mozilla.com/report/index/635ae815-847f-4339-97b6-8b9372091110
And it looks like every single crash is on Windows NT 5.1.2600, which I think means XP.
And there's 3 of these crashes reported on trunk as well, so likely a problem there too, just not seen as much yet due to the small number of users there still.
This is a crash regression, I think we should attempt to fix this before 1.9.2 goes out the door.
Flags: blocking1.9.2?
Reporter | ||
Comment 1•15 years ago
|
||
Dbaron mentioned that this might be related to the fix for bug 521750.
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 3•15 years ago
|
||
Interesting to see this in a non-embedding situation, unless somebody is using a xulrunner stub with the Firefox libxul or something else weird like that.
Updated•15 years ago
|
Summary: New nsThreadManager::Init() startup crash in 3.5.5 → New startup crash [@ nsThreadManager::Init()] in 3.5.5
Updated•15 years ago
|
Flags: blocking1.9.2?
Updated•14 years ago
|
status1.9.1:
? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•