Daily 19.0a1 crashes on launch due to ABI incompatibility - requires new Darwin_x86_64-gcc3 Lightning build



Build Config
5 years ago
5 years ago


(Reporter: Guillermo Huerta [Disabled MoCo account], Unassigned)



Mac OS X


(crash signature)


(1 attachment)

Daily downloaded the upgrade and I then clicked to apply it.  When it went to relaunch, Daily crashed.  Everytime after that it would crash on boot.

Comment 1

5 years ago
Thanks for taking the time to report this!
Please follow the steps on http://support.mozillamessaging.com/kb/thunderbird-crashes and report back here. Thanks!
Flags: needinfo?(ghuerta)
Created attachment 678370 [details]
Daily Crash Reports

I'm still seeing the crashes on Today's Daily.  I've attached the crash id of the 5 crashes I've seen.
Flags: needinfo?(ghuerta)
0 		@0x7fff65cb309d 	
1 	libdyld.dylib 	libdyld.dylib@0x8ed 	
2 	XUL 	XPCConvert::NativeInterface2JSObject 	
3 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
4 	libcalbasecomps.dylib 	calDateTime::SetJsDate 	calendar/base/src/calDateTime.cpp:636
5 	XUL 	NS_InvokeByIndex_P 	xptcinvoke_x86_64_unix.cpp:162
6 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
7 	XUL 	XPCWrappedNative::CallMethod 	XPCWrappedNative.cpp:3118
8 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
9 	XUL 	mozilla::dom::CSS2PropertiesBinding::set_borderImageOutset 	CSS2PropertiesBinding.cpp:2072
10 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
11 	XUL 	nsThreadManager::GetIsMainThread 	nsThreadManager.cpp:272
12 	XUL 	NS_IsMainThread_P 	nsThreadUtils.cpp:120
13 	XUL 	nsXPConnect::GetXPConnect 	nsXPConnect.cpp:140
14 	XUL 	XPCCallContext::~XPCCallContext 	xpcprivate.h:666
15 	XUL 	js::ObjectImpl::nativeLookup 	ObjectImpl.cpp:265
16 	XUL 	CallAddPropertyHook 	jscntxtinlines.h:437
17 	XUL 	js::DefineNativeProperty 	Barrier-inl.h:318
18 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
19 	XUL 	XPCWrappedNative::GetWrappedNativeOfJSObject 	XPCWrappedNative.cpp:1824
20 	XUL 	XPCCallContext::Init 	xpcpublic.h:151
21 	XUL 	XPCCallContext::XPCCallContext 	XPCCallContext.cpp:31
22 	XUL 	XPC_WN_GetterSetter 	xpcprivate.h:2803
23 	XUL 	NS_IsMainThread_P 	nsThreadUtils.cpp:120
24 	XUL 	js::InvokeKernel 	jscntxtinlines.h:364
25 	XUL 	XPCCallContext::~XPCCallContext 	XPCCallContext.cpp:328
26 	XUL 	XPC_WN_NoMods_Proto_Resolve 	XPCWrappedNativeJSOps.cpp:1743
27 	XUL 	js::ContextStack::pushInvokeArgs 	jsutil.h:195
28 	XUL 	js::Invoke 	jsinterp.h:109
29 	XUL 	js::InvokeGetterOrSetter 	jsinterp.cpp:485
30 	XUL 	js::Shape::set 	jsscopeinlines.h:313
31 	XUL 	js::baseops::SetPropertyHelper 	jsobj.cpp:4613
32 	XUL 	XPCVariant::GetAsInt16 	XPCVariant.cpp:690
33 	XUL 	js::PropertyCache::fullTest 	jspropertycache.cpp:111
34 	XUL 	js::SetPropertyOperation 	jsobjinlines.h:94
35 	XUL 	js::GetPropertyOperation 	jsinterpinlines.h:287
36 	XUL 	js::Interpret 	jsinterp.cpp:2231
37 	XUL 	SearchTable 	pldhash.cpp:402
38 	XUL 	SearchTable 	pldhash.cpp:435
39 	XUL 	xpc::EnsureCompartmentPrivate 	xpcprivate.h:4337
40 	XUL 	XPCConvert::NativeInterface2JSObject 	XPCConvert.cpp:857
41 	XUL 	NS_TableDrivenQI 	nsISupportsImpl.cpp:16
42 	XUL 	nsIViewManager::COMTypeInfo<int>::kIID 	
43 	libnspr4.dylib 	PR_GetCurrentThread 	ptthread.c:583
44 	XUL 	NS_IsMainThread_P 	nsThreadUtils.cpp:120
45 	XUL 	nsXPConnect::GetXPConnect 	nsXPConnect.cpp:140
46 	XUL 	CallMethodHelper::~CallMethodHelper

By looking at this it seems lightning is the culprit.
Crash Signature: @0x7fff65cb309d libdyld.dylib@0x8ed
Component: General → General
Product: Thunderbird → Calendar
Severity: normal → critical
Keywords: crash

Comment 4

5 years ago
There were some ABI changes in Thunderbird Core recently. Please ensure that you are using the most current Lightning 2.1a1 nightly build that matches Thunderbird. For your platform it should be https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-central/lightning-2.1a1.en-US.mac.xpi
I'm using 2.1a1.  Is there anyway to find out what build of lightning?
Also the version of lightning that you linked says incompatible with Daily 19.0a1 and won't let me install.

Comment 7

5 years ago
Open Tools > Add-ons > Extensions, select Lightning and choose About... from context menu. The popup dialog will show you the Build ID of Lightning.

Same information is available in you profile folder "...\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103}\application.ini".
I'm using lightning 2.1a1 build 20121030031003

Comment 9

5 years ago
The build is too old and incompatible with newer Thunderbird builds causing the problem.

It seems the current Lightning packages support only Darwin_x86-gcc3 platform. Support for Darwin_x86_64-gcc3 platform is missing / broken. I added Bug 793628 Comment 25.
That was the build I got updated to on Thursday, I'll uninstall and re-add after upgrading.

Comment 11

5 years ago
Latest Lightning-Nightlys (20121111)(In reply to Stefan Sitter from comment #4)
> There were some ABI changes in Thunderbird Core recently. Please ensure that
> you are using the most current Lightning 2.1a1 nightly build that matches
> Thunderbird. For your platform it should be
> https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-
> comm-central/lightning-2.1a1.en-US.mac.xpi

latest-comm-central/lightning-2.1a1.en-US.mac.xpi cannot installed in latest Daily 19a1, "because it is not comatible with Daily 19.a1".


Comment 12

5 years ago
It's being worked on in Bug 793628, see Comment 9 above.
Depends on: 793628
Summary: Latest Daily 19.01 crashes on launch → Daily 19.0a1 crashes on launch due to ABI incompatibility - requires new Darwin_x86_64-gcc3 Lightning build
Component: General → Build Config

Comment 13

5 years ago
According to Bug 793628 the problem ought to be fixed. Could you retest using Lightning 2.1a2 with Thunderbird 19.0a2 ("Earlybird") or using Lightning 2.2a1 with Thunderbird 20.0a1 ("Daily")?
Yep, confirmed this is working using 2.2a1 on 20.0a1

Comment 15

5 years ago
Fixed by attachment 681904 [details] [diff] [review] in bug 793628.
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.1
You need to log in before you can comment on or make changes to this bug.