Closed Bug 691279 Opened 14 years ago Closed 14 years ago

crash __libc_android_abort | Java_org_mozilla_gecko_GeckoAppShell_reportJavaCrash

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Version:
Firefox 7
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(fennec-)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
fennec - ---

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

It's #4 top crasher in Fennec 7.0. It might be related to bug 683461 although stack traces are different. Stack traces look like: Frame Module Signature [Expand] Source 0 libc.so __libc_android_abort 1 libxul.so Java_org_mozilla_gecko_GeckoAppShell_reportJavaCrash widget/src/android/AndroidJNI.cpp:166 2 libmozutils.so Java_org_mozilla_gecko_GeckoAppShell_reportJavaCrash other-licenses/android/APKOpen.cpp:242 3 libdvm.so dvmPlatformInvoke 4 libdvm.so dvmCallJNIMethod_general 5 libdvm.so dvmResolveNativeMethod 6 libdvm.so dvmAsmSisterStart 7 libdvm.so dvmMterpStd 8 libdvm.so dvmInterpret 9 libdvm.so dvmInvokeMethod 10 libdvm.so dvmFreeDexOrJar 11 libdvm.so dvmAsmSisterStart 12 libdvm.so dvmMterpStd 13 libdvm.so dvmInterpret 14 libdvm.so dvmCallMethodV 15 libdvm.so JNI_CreateJavaVM ... More reports at: https://crash-stats.mozilla.com/report/list?signature=__libc_android_abort%20|%20Java_org_mozilla_gecko_GeckoAppShell_reportJavaCrash
I'm totally confused why we're not seeing Java exception stacks here. Ted, would this have something to do with the "WARNING: JSON file missing CrashTime; WARNING: No 'client_crash_date' could be determined from the Json file" processor note?
I really don't know why that's missing. The raw JSON has a bunch of other information, so it's not as though we failed to write it out completely.
tracking-fennec: --- → ?
Any java crash should have this signature, so its not really the #4 top crasher unless the java stacks are the same as well. Not having the java stacks is obviously concerning.
this bug doesn't track because this could be a whole bunch of one off java crashes, we just don't know. I'll file a bug for not having java crash stack data and follow up with ted on it.
tracking-fennec: ? → -
Looks like we are reporting, but Socorro isn't showing the information. Bug 692185
There have been no crashes for the last four weeks. I close it as WFM.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.