Closed Bug 362225 Opened 18 years ago Closed 18 years ago

crash while displaying "xx new messages" alert

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tonymec, Assigned: mscott)

References

Details

(Keywords: crash, regression)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061129 SeaMonkey/1.5a
Build Identifier: "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1pre) Gecko/20061129 Thunderbird/2.0b1pre" - Build ID: 2006112903

TB26653295G

This bug did not happen in yesterday's nightly.


Reproducible: Always

Steps to Reproduce:
1. Tick "Edit => Preferences => General => When new messages arrive: [x] Show an alert
2. Wait for new mail to arrive


Actual Results:  
crash. Talkback comes up but Thunderbird does not die. When clicking window-close X at top right, after some time a popup apears, saying that "thunderbird-bin" is not responding, and offering to kill it, which will lose all unsaved data.

Expected Results:  
no crash

Talkback report:

Incident ID: 26653295
Stack Signature	js_GetGCThingFlags() d8606d5d
Product ID	Thunderbird2
Build ID	2006112903
Trigger Time	2006-11-29 07:09:55.0
Platform	LinuxIntel
Operating System	Linux 2.6.11.4-21.14-default
Module	libmozjs.so + (000446cf)
URL visited	
User Comments	crash at startup on "xx new messages" alert
Since Last Crash	0 sec
Total Uptime	1 sec
Trigger Reason	SIGSEGV: Segmentation Fault: (signal 11)
Source File, Line No.	/builds/tinderbox/Tb-Mozilla1.8/Linux_2.4.18-14_Depend/mozilla/js/src/jsgc.c, line 492
Stack Trace 	
js_GetGCThingFlags()  [mozilla/js/src/jsgc.c, line 492]
js_MarkGCThing()  [mozilla/js/src/jsgc.c, line 2447]
JS_MarkGCThing()  [mozilla/js/src/jsapi.c, line 1863]
WrappedNativeJSGCThingMarker()  [mozilla/js/src/xpconnect/src/xpcwrappednativescope.cpp, line 1856]
JS_DHashTableEnumerate()  [mozilla/js/src/jsdhash.c, line 675]
XPCWrappedNativeScope::FinishedMarkPhaseOfGC()  [mozilla/js/src/xpconnect/src/xpcwrappednativescope.cpp, line 265]
XPCJSRuntime::GCCallback()  [mozilla/js/src/xpconnect/src/xpcjsruntime.cpp, line 333]
DOMGCCallback()  [mozilla/dom/src/base/nsJSEnvironment.cpp, line 2272]
js_GC()  [mozilla/js/src/jsgc.c, line 2967]
JS_GC()  [mozilla/js/src/jsapi.c, line 1884]
nsJSContext::Notify()  [mozilla/dom/src/base/nsJSEnvironment.cpp, line 2229]
nsTimerImpl::Fire()  [mozilla/xpcom/threads/nsTimerImpl.cpp, line 398]
handleTimerEvent()  [mozilla/xpcom/threads/nsTimerImpl.cpp, line 462]
PL_HandleEvent()  [mozilla/xpcom/threads/plevent.c, line 688]
PL_ProcessPendingEvents()  [mozilla/xpcom/threads/plevent.c, line 623]
nsEventQueueImpl::ProcessPendingEvents()  [mozilla/xpcom/threads/nsEventQueue.cpp, line 421]
event_processor_callback()  [mozilla/widget/src/gtk2/nsAppShell.cpp, line 71]
libglib-2.0.so.0 + 0x4a69f (0x4065069f)
libglib-2.0.so.0 + 0x23967 (0x40629967)
libglib-2.0.so.0 + 0x25ce2 (0x4062bce2)
libglib-2.0.so.0 + 0x26cf7 (0x4062ccf7)
libgtk-x11-2.0.so.0 + 0x116be3 (0x40329be3)
nsAppShell::Run()  [mozilla/widget/src/gtk2/nsAppShell.cpp, line 141]
nsAppStartup::Run()  [mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 152]
XRE_main()  [mozilla/toolkit/xre/nsAppRunner.cpp, line 848]
main()  [mozilla/mail/app/nsMailApp.cpp, line 63]
libc.so.6 + 0x14e80 (0x40af0e80)
*** Bug 362215 has been marked as a duplicate of this bug. ***
Keywords: crash
the fact that the system was at high load (about 3 or higher according to the "Load Average (1 min)" display in ksysguard) may be relevant.
Confirming... One would guess has to do with bug 332160 landing yesterday. My 2006-11-29 branch build always crashes when I get new mail now. (Trunk works just fine.) Turn off the "show alert", and all is ok. 

I might add I didn't see this problem when I tested that fix on branch like a month ago.

Here are some of the crashes, looks to be all in different places: TB26661170W TB26661539H TB26661205E TB26660957X. 
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → 2.0
Keywords: regression
(In reply to comment #3)
[...]
> Here are some of the crashes, looks to be all in different places: TB26661170W
> TB26661539H TB26661205E TB26660957X. 

The crashes mentioned under bug 362215 also seem to be in various places.
I've backed out Bug 332160 on the branch where this was crashing.
Blocks: 332160
(In reply to comment #5)
> I've backed out Bug 332160 on the branch where this was crashing.
> 

"Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1pre) Gecko/20061130 Thunderbird/2.0b1pre" - Build ID: 2006113004

No crash. But (like until day before yesterday) no alert display either.
This was fixed when Scott backed out the patch for bug 332160. ->FIXED
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
(In reply to comment #7)
> This was fixed when Scott backed out the patch for bug 332160. ->FIXED
> 

I propose to wait until the new fix for bug 332160 lands on the Tb-2.0 beta builds, and then mark this bug VERIFIED after ascertaining that that new fix does not reawaken the crash.
Fix for bug 332160 landed on 1.8.1.1 branch between 20061206 and 20061207 rounds of nightly builds while I was asleep. Just saw the new alert slider. No crash.

I'm marking this bug as VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.