721862 - TB10 crashes immediately on launch.

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Chris Ramsden]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20120124122804

Steps to reproduce:

Install TB10 from PPA: http://ppa.launchpad.net/mozillateam/thunderbird-next/ubuntu





Actual results:

Crashes immediately when run. Both normal and safe mode. 


Expected results:

It shouldn't crash. ;)
Same version runs fine on similar Linux installation on other computer.

Comment 1

[Wayne Mery (:wsmwk)]

no more info than this?
can you cc someone @ubuntu

Comment 2

[Ludovic Hirlimann [:Usul]]

Chris could you get a stack trace ?

Comment 3

[Chris Ramsden]

Attachment: stack trace

Stack trace as requested.

Comment 4

[Chris Ramsden]

Maybe we should close this one. 

It appears to be add-on related. It crashes in safe mode, but manually removing the extensions folder allowed it to run normally. I've been adding them back in and it's still running. I'll report back here if I can demonstrate that one particular add-on has caused this.

Comment 5

[David Mandelin [:dmandelin]]

This might be a dup of bug 716232.

Comment 6

[Tony Mechelynck [:tonymec]]

(In reply to David Mandelin from comment #5)
> This might be a dup of bug 716232.

I don't think so, bug 716232 is a regression happening in Gecko 12 dated 2012-01-06 (starting at mozilla-central changeset faf5f8842fec) and later builds. The present crash is found in Thunderbird 10, which ought to be immune from bug 716232.

Comment 7

[David Mandelin [:dmandelin]]

(In reply to Tony Mechelynck [:tonymec] from comment #6)
> (In reply to David Mandelin from comment #5)
> > This might be a dup of bug 716232.
> 
> I don't think so, bug 716232 is a regression happening in Gecko 12 dated
> 2012-01-06 (starting at mozilla-central changeset faf5f8842fec) and later
> builds. The present crash is found in Thunderbird 10, which ought to be
> immune from bug 716232.

Ah, OK. Thanks for the correction.

Comment 8

[David Mandelin [:dmandelin]]

(In reply to Chris Ramsden from comment #4)
> Maybe we should close this one. 
> 
> It appears to be add-on related. It crashes in safe mode, but manually
> removing the extensions folder allowed it to run normally. I've been adding
> them back in and it's still running. I'll report back here if I can
> demonstrate that one particular add-on has caused this.

Yes, if you can pinpoint one add-on, please do let us know. It could help us figure out whether it's a JS engine bug we should fix, or something in the add-on we should contact the authors about.

Comment 9

[Wayne Mery (:wsmwk)]

(In reply to David Mandelin [:dmandelin] from comment #8)
> Yes, if you can pinpoint one add-on, please do let us know. It could help us
> figure out whether it's a JS engine bug we should fix, or something in the
> add-on we should contact the authors about.

Chris did you get this sorted out?

Comment 10

[Wayne Mery (:wsmwk)]

(In reply to Wayne Mery (:wsmwk) from comment #9)
> (In reply to David Mandelin [:dmandelin] from comment #8)
> > Yes, if you can pinpoint one add-on, please do let us know. It could help us
> > figure out whether it's a JS engine bug we should fix, or something in the
> > add-on we should contact the authors about.
> 
> Chris did you get this sorted out?

Comment 11

[Wayne Mery (:wsmwk)]

The crash signature is gone, no crashes newer than version 29 on crash-stats.
eg bp-42723bc7-0f32-4239-9ff4-a6d4f2160106