Closed
Bug 419035
Opened 16 years ago
Closed 16 years ago
[1.8 branch only] "Random" crash when I want to display a mail
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: steven.demierre, Assigned: mkmelin)
References
()
Details
(Keywords: fixed1.8.1.13)
Attachments
(2 files)
105.90 KB,
text/plain
|
Details | |
1.16 KB,
patch
|
tony
:
review+
dveditz
:
approval1.8.1.13+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.12) Gecko/20080129 Iceweasel/2.0.0.12 (Debian-2.0.0.12-1) Build Identifier: 2.0.0.9-3 (sorry, no build identifier...) The problem appears with Icedove, the Debian branded version of Thunderbird (but i think the error is more general, likely afflicting the whole Mozilla suite) When i single-click on some mails to display them, Thunderbird crashes with Sigsegv. I've attached gdb and traced the error down to line nr. 864 in mozilla/toolkit/components/url-classifier/src/nsUrlClassifierDBService.cpp (version 1.1.2.15). The variable gMonitor is NULL, because the call on line 841 fails and so gMonitor is never initialized. I don't know yet why the init() call fails, but probably, gMonitor should be chechked for NULL in the destructor anyway. Reproducible: Sometimes Steps to Reproduce: 1. Open Thunderbird 2. Click on an email in the main window 3. -> Crash I can fix this problem for some minutes/hours by reinstalling Thunderbird with my package manager, but then it happens again (and for all mails until i reinstall it). The bug is the same as https://bugs.launchpad.net/ubuntu/+source/mozilla-thunderbird/+bug/131557 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425564
Reporter | ||
Comment 1•16 years ago
|
||
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 2.0
Reporter | ||
Comment 2•16 years ago
|
||
The bug disappears when i disable the Lightning extension (Version 0.7). However, this is not really a solution, as i want to have Lightning enabled.
Assignee | ||
Comment 3•16 years ago
|
||
I wonder if PR_DestroyMonitor should null-check... http://lxr.mozilla.org/seamonkey/source/nsprpub/pr/src/threads/prmon.c#84
Assignee | ||
Comment 4•16 years ago
|
||
timeless tells me nspr requires that you not pass null. The code is very different on trunk, I don't think the crash is an issue there.
Summary: "Random" crash when I want to display a mail → [1.8 only] "Random" crash when I want to display a mail
Assignee | ||
Comment 5•16 years ago
|
||
How does this look? it would be null at least if Init() failed early.
Assignee: nobody → mkmelin+mozilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #306349 -
Flags: review?(tony)
Comment 6•16 years ago
|
||
Comment on attachment 306349 [details] [diff] [review] proposed fix I think that's fine, but it would be nice to know why this is happening. Once we know why, we could add a comment explaining why we need this check.
Attachment #306349 -
Flags: review?(tony) → review+
Assignee | ||
Updated•16 years ago
|
Attachment #306349 -
Flags: approval1.8.1.13?
Reporter | ||
Comment 7•16 years ago
|
||
I'll try to do some more debugging tomorrow and maybe i can tell you, why it happens.
Comment 8•16 years ago
|
||
Comment on attachment 306349 [details] [diff] [review] proposed fix approved for 1.8.1.13, a=dveditz,dmose for release-drivers
Attachment #306349 -
Flags: approval1.8.1.13? → approval1.8.1.13+
Assignee | ||
Comment 9•16 years ago
|
||
Checked in on the 1.8 branch: Checking in toolkit/components/url-classifier/src/nsUrlClassifierDBService.cpp; /cvsroot/mozilla/toolkit/components/url-classifier/src/nsUrlClassifierDBService.cpp,v <-- nsUrlClassifierDBService.cpp new revision: 1.1.2.16; previous revision: 1.1.2.15 done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Keywords: fixed1.8.1.13
Resolution: --- → FIXED
Summary: [1.8 only] "Random" crash when I want to display a mail → [1.8 branch only] "Random" crash when I want to display a mail
Comment 10•16 years ago
|
||
Is there a repro case that I or someone else in QA can run for this? It is otherwise difficult to verify the fix for the release.
You need to log in
before you can comment on or make changes to this bug.
Description
•