Thunderbird crashes when idle (JS_ValueToECMAUint32 in stack trace)

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
9 years ago
9 years ago

People

(Reporter: sfink, Unassigned)

Tracking

({crash, stackwanted})

1.8 Branch
x86
Linux
crash, stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: 

When I leave Thunderbird open for a day or two, I'll come back to find it has crashed. This time I ran it under the debugger to get a stack trace out.


Reproducible: Sometimes

Steps to Reproduce:
1. Run thunderbird
2. Open my mailbox (talking to an Exchange server)
3. Wait
Actual Results:  
Fall down go boom. This run at least, reported a segmentation fault.

Expected Results:  
Stay up no boom.
(Reporter)

Comment 1

9 years ago
Thunderbird version 2.0.0.22 (20090625)
(Reporter)

Comment 2

9 years ago
Created attachment 404093 [details]
Stack trace

Comment 3

9 years ago
The current version of Thunderbird is 2.0.0.23. Can you update to that and see if you can reproduce? The stack trace of an optimized build isn't that useful. Can you submit the talkback report for the crash. We still do get talkback reports for Thunderbird?

the 1.8.1 branch isn't supported any more except for thunderbird. I doubt such a low frequency crash will get much attention.
Version: unspecified → 1.8 Branch

Comment 4

9 years ago
Also, Steve, can you reproduce using version 3 beta? 
 backup your profile before using
 http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/
Keywords: crash

Updated

9 years ago
Keywords: stackwanted
(Reporter)

Comment 5

9 years ago
It has now been running successfully for about 10 days with 3.0b4, which is much longer than I ever managed before. So I'm happy to consider it fixed.

Should I mark my own bug resolved in this case, or allow someone else?

Thanks.
(In reply to comment #5)
> Should I mark my own bug resolved in this case, or allow someone else?

Please feel free to resolve as WORKSFORME, in this case it's set.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.