It's #2 top crasher in 17.0b1.
Signature XREMain::XRE_mainStartup More Reports Search
Date Processed 2012-10-12 08:14:56
Install Age 1.0 minutes since version was first installed.
Install Time 2012-10-12 08:13:21
Build ID 20121010211745
Release Channel beta
OS Version 0.0.0 Linux 3.0.15-928452-user #1 SMP PREEMPT Tue Jul 31 19:37:49 KST 2012 armv7l
Build Architecture arm
Build Architecture Info
Crash Reason SIGSEGV
Crash Address 0x0
Processor Notes WARNING: JSON file missing Add-ons
Adapter Vendor ID
Adapter Device ID
Device samsung GT-I9300
Android API Version 15 (REL)
Android CPU ABI armeabi-v7a
Frame Module Signature Source
0 libxul.so XREMain::XRE_mainStartup toolkit/xre/nsAppRunner.cpp:3445
1 libxul.so XREMain::XRE_main toolkit/xre/nsAppRunner.cpp:3869
2 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:3963
3 libxul.so GeckoStart toolkit/xre/nsAndroidStartup.cpp:73
4 libmozglue.so Java_org_mozilla_gecko_GeckoAppShell_nativeRun APKOpen.cpp:983
5 libdvm.so libdvm.so@0x1ed72
6 dalvik-heap (deleted) dalvik-heap @0xdf44c6
7 libdvm.so libdvm.so@0x5902d
8 data@firstname.lastname@example.org_betaemail@example.com data@firstname.lastname@example.org_betaemail@example.com@0x141382
More reports at:
Do we have any co-relations and do we see this on other any other channels ?
This appears to be a null mProfileLock, which basically means that http://hg.mozilla.org/releases/mozilla-beta/annotate/f02c5fb11741/toolkit/xre/nsAppRunner.cpp#l3430 succeeded but didn't return a profile lock.
Does this have a nightly regression range?
(In reply to bhavana bajaj [:bajaj] from comment #1)
> Do we have any co-relations and do we see this on other any other channels ?
Crashes happen before any loaded extensions, on Froyo, Gingerbread, ICS and JB.
Two Mac users were affected in 15.0.1.
(In reply to Benjamin Smedberg [:bsmedberg] from comment #2)
> Does this have a nightly regression range?
No, because only Beta users and one Aurora user are affected.
Tracking for now and assigning to Benjamin - is it possible to hunt down a regression in Beta? If you're not the right person for this please reassign to another person but if we're going to track for 17 it needs to be assigned to someone.
I do not have time to look at this bug. I suspect it's something with the locked profile dialog which can't be shown on Android, but I'd like somebody from the mobile team to take it if necessary.
Alright - over to Brad then for a mobile team assessment of who can take this on.
Wes - Does this seem similar to the other bug you fixed related to locked profiles?
Yes. I have a fix. testing it now
Created attachment 672850 [details] [diff] [review]
I'm not exactly sure how to reproduce this bug, but this should fix it.
Comment on attachment 672850 [details] [diff] [review]
[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 795053
User impact if declined: Crashes on startup. Subsequent starts should work
Testing completed (on m-c, etc.): Landed on mc today
Risk to taking this patch (and alternatives if risky): Medium because it gets hit during startup. This should be doing the same thing we would do in other cases where we unlock the profile for the user (i.e. a few lines above this patch).
String or UUID changes made by this patch: None.