Thunderbird 31.1.1 crashing @ EnterBaseline on launch on OS X 10.9.4 after upgrade from Thunderbird 24
It never comes up, just gives the crash report. Crash reports are
bp-a02fe4b1-cc38-4204-9c6f-6003f2140916 14-09-16 12:30 bp-d6738939-695a-438a-86b7-a610c2140916 14-09-16 12:30
and the same for v 30.0:
bp-308d3ab7-eb72-4b49-8628-48f952140725 14-07-25 10:36 bp-d507806f-6e18-4f03-bef5-076af2140725 14-07-25 10:34
由 Wayne Mery 於
所有回覆 (20)
Of course, the OS X version is 10.8.5... (be careful what you copy)
@ EnterBaseline crash is extremely rare, only 3-4 crashes in a week for several million users. It might be https://bugzilla.mozilla.org/show_bug.cgi?id=1034706. No ETA on fix
I don't have a solution, but you might try starting in *Windows'* safe mode with networking enabled - win8 http://windows.microsoft.com/en-US/windows-8/windows-startup-settings-including-safe-mode - win7 http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode - XP http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx
Still In Windows safe mode, start thunderbird in safe mode - http://support.mozillamessaging.com/en-US/kb/safe-mode
Does problem go away?
It is kinda difficult to go into a safe Windows mode under OS X, but I managed to start the Thunderbird in safe mode. Trying to figure out what might be wrong I disabled a dictionary (the only add-on apart from plugins) and deleted (well - mis-named) localstore.rdf. After that change I tried a normal Thunderbird start but got a COS (crash on start-up) again. Just to mention it again: this is Thunderbird 3.1.1. As a differential diagnostics: Firefox 32.0.1 (and 31 before that) never had a problem.
Oops! Of course Thunderbird 31.1.1 - too many 1s...
hmm, your last crash bp-8c14f3f6-8f4d-4a6d-af1e-3ad402140917 is different, but still blowing up in js - js::jit::IonCannon(JSContext*, js::RunState&) which is https://bugzilla.mozilla.org/show_bug.cgi?id=985001
Does it stop ifyou go back to http://download.cdn.mozilla.net/pub/mozilla.org/thunderbird/releases/31.1.0/ or http://download.cdn.mozilla.net/pub/mozilla.org/thunderbird/releases/31.0/ and turn off automatic updates?
http://download.cdn.mozilla.net/pub/mozilla.org/thunderbird/releases/31.1.0/ produces bp-0a6aa14a-41d2-450b-ac9d-7878e2140921 and http://download.cdn.mozilla.net/pub/mozilla.org/thunderbird/releases/31.0/ produces bp-0769274f-f0d3-417f-9c2e-add4d2140921
As far as automatic updates go I am using "Ask me what I want to do"
I hate to ask more of you. But could you test the beta versions at http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/ and see which ones work and which fail? Start with 27.0b1 and then take the next midpoint between a version that work and version that doesn't (binary search) until you know version N works and version N+1 doesn't work.
25.0b1/ 26.0b1/ 27.0b1/ 28.0b1/ 29.0b1/ 30.0b1/
29.0b1 works, 30.0b1 crashes
(and I don't hate doing this, because I understand why you are asking)
Oh, yeah; the report for the 30.0b1 crash is: bp-e412d9d7-6c10-4abb-bbac-ec3412140922 (must be getting old, always forgetting something...)
Great work. Can you cc youself to https://bugzilla.mozilla.org/show_bug.cgi?id=985001
The good folks at https://bugzilla.mozilla.org/show_bug.cgi?id=985001 have asked if you can narrow the regression range further.
If 29.0b1 works, 30.0b1 crashes then (to be on the safe side) the range you want to binary search is http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014/02/2014-02-03-03-02-02-comm-central/ (the last 29.0a1, which we should expect to work) to http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014/03/2014-03-18-03-02-03-comm-central/ (the last 30.0a1, which we should expect to fail).
[Edit: Actually, in theory it's possible that the last 30.0a1 crashes. But the first 31.0a1 should not http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014/03/2014-03-19-03-02-02-comm-central/ ]
Let me know if you need help. I hope this helps nail the sucker which caused this.
由 Wayne Mery 於
Also, it may be interesting to know if the crash on startup goes away if you use
-offlline
on the command line when you start up.
Right. So 1st: do I see it correctly that to "cc myself to" the bug I must have a Bugzilla account first?
2nd:
> If 29.0b1 works, 30.0b1 crashes then (to be on the safe side) the range > you want to binary search is http://ftp.mozilla.org/... (the last 29.0a1, > which we should expect to work) to http://ftp.mozilla.org/... (the last > 30.0a1, which we should expect to fail).
Yes, 29.0a1 works (has to - it precedes 29.0b1), and 30.0a1 crashes. As you asked I tried 30.a1 with -offline and it comes up OK. I also tried -offline with 31.1.1 and it comes up just fine.
I am not sure about the systematics of the directory to be able to choose the right bisection objects. Could you explain:
/pub/mozilla.org/thunderbird/nightly/2014/02 that's clear (February)
but then it goes on with ... 2014-02-03-03-02-02-comm-central/ which you suggested and 2014-02-04-00-40-03-comm-aurora/ which is unclear to me except for being from the 4th Feb. 2014.
What's the deal with comm-central vs. comm-aurora and what's
the meaning of 03-02-02 vs. 00-40-03? Which should I pick? Just the comm-central? (Any comm-central?)
Right, never mind the above.
30.0a1 from .../2014-03-18-03-02-03-comm-central/ runs 31.0a1 from .../2014-03-19-03-02-02-comm-central/ crashes
(both http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014/03/)
由 gmsF 於
...and for the hell of it
30.0a2 from .../2014-03-18-05-44-44-comm-aurora/ crashes 30.0a2 from .../2014-03-19-00-40-01-comm-aurora/ crashes
hmm...
A question, not a cure.
How long is it since the machine has actually been cold started?
Anything between 5 minutes and 2 hours (it's a laptop which I actually shut down when not in use).
Also for the testing I shut down all programs except for Terminal, but it crashes even when Terminal is not running. (of course Finder and all the rest of the system is running)
For all it's worth (2c? 1/2c?):
35.0a1 from .../2014-09-22-03-02-03-comm-central/ crashes
gmsF,
A crash of this type was fixed in version 31. Are you still crashing?
In the meantime I moved from OS X to Fedora, but if you tell me in which version the problem is fixed, I can test it on the old machine. Oops. It is now running Yosemite, so the comparison will not be valid anyway...
Well, "solved the problem by moving from Mac to Linux" couple of months back. Does it count as "solved"?