Closed Bug 746926 Opened 12 years ago Closed 9 years ago

crash in mozilla::AndroidBridge::GetMimeTypeFromExtensions

Categories

(Core Graveyard :: Widget: Android, defect)

ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [native-crash])

Crash Data

It first appeared in 14.0a1/20120322.

Signature 	mozilla::nsJNIString::nsJNIString More Reports Search
UUID	93ba85a3-6279-49a4-ac84-5c90d2120419
Date Processed	2012-04-19 03:18:09
Uptime	548
Last Crash	10.2 minutes before submission
Install Age	2.7 hours since version was first installed.
Install Time	2012-04-19 00:35:09
Product	FennecAndroid
Version	14.0a1
Build ID	20120418052015
Release Channel	nightly
OS	Linux
OS Version	0.0.0 Linux 2.6.35.7+ #1 SMP PREEMPT Wed Mar 21 19:30:26 UTC 2012 armv7l
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x9
App Notes 	
EGL? EGL+ AdapterVendorID: omap4430, AdapterDeviceID: Kindle Fire.
AdapterDescription: 'Android, Model: 'Kindle Fire', Product: 'blaze', Manufacturer: 'Amazon', Hardware: 'omap4430''.
GL Context? GL Context+ GL Layers? GL Layers+ WebGL? WebGL+ 
Amazon Kindle Fire
generic/blaze/blaze:2.3.4/GINGERBREAD/6.3_user_4019920:user/release-keys
EMCheckCompatibility	True

Frame 	Module 	Signature 	Source
0 	libdvm.so 	libdvm.so@0x54b14 	
1 	libxul.so 	mozilla::nsJNIString::nsJNIString 	jni.h:834
2 	libxul.so 	mozilla::AndroidBridge::GetMimeTypeFromExtensions 	widget/android/AndroidBridge.cpp:564
3 	libxul.so 	nsMIMEInfoAndroid::GetMimeInfoForFileExt 	uriloader/exthandler/android/nsMIMEInfoAndroid.cpp:113
4 	libxul.so 	nsOSHelperAppService::GetMIMEInfoFromOS 	uriloader/exthandler/android/nsOSHelperAppService.cpp:64
5 	libxul.so 	nsExternalHelperAppService::GetTypeFromExtension 	uriloader/exthandler/nsExternalHelperAppService.cpp:2602
6 	libxul.so 	nsExternalHelperAppService::GetTypeFromURI 	uriloader/exthandler/nsExternalHelperAppService.cpp:2687
7 	libxul.so 	nsUnknownDecoder::SniffURI 	netwerk/streamconv/converters/nsUnknownDecoder.cpp:541
8 	libxul.so 	nsUnknownDecoder::DetermineContentType 	netwerk/streamconv/converters/nsUnknownDecoder.cpp:383
9 	libxul.so 	nsUnknownDecoder::OnStopRequest 	netwerk/streamconv/converters/nsUnknownDecoder.cpp:240
10 	libxul.so 	nsHttpChannel::OnStopRequest 	netwerk/protocol/http/nsHttpChannel.cpp:4495
11 	libxul.so 	nsInputStreamPump::OnStateStop 	netwerk/base/src/nsInputStreamPump.cpp:587
12 	libxul.so 	nsInputStreamPump::OnInputStreamReady 	netwerk/base/src/nsInputStreamPump.cpp:405
13 	libxul.so 	nsInputStreamReadyEvent::Run 	xpcom/io/nsStreamUtils.cpp:114
14 	libxul.so 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:656
15 	libxul.so 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:245
16 	libxul.so 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:110
17 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:208
18 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:201
19 	libxul.so 	nsBaseAppShell::Run 	widget/xpwidgets/nsBaseAppShell.cpp:189
20 	libxul.so 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:295
21 	libxul.so 	XREMain::XRE_mainRun 	toolkit/xre/nsAppRunner.cpp:3768
22 	libxul.so 	XREMain::XRE_main 	toolkit/xre/nsAppRunner.cpp:3845
23 	libxul.so 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3921
...

More reports at:
https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3AnsJNIString%3A%3AnsJNIString
I believe this crash is a dupe of bug 721654, which blassey fixed recently.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
The stack is completely different.
Moreover, bug 721654 is fixed from 14.0a1/20120418 while these crashes happen after.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
There is bug 694992 which also has a stack like this in the summary (among other stacks).
Crash Signature: [@ mozilla::nsJNIString::nsJNIString] → [@ mozilla::nsJNIString::nsJNIString] [@ dvmStringLen | JNI_CreateJavaVM | mozilla::nsJNIString::nsJNIString]
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → DUPLICATE
Here is a recent crash: bp-1b09332c-d5c7-4baf-8d44-36fb52120606.
Status: RESOLVED → REOPENED
Crash Signature: [@ mozilla::nsJNIString::nsJNIString] [@ dvmStringLen | JNI_CreateJavaVM | mozilla::nsJNIString::nsJNIString] → [@ mozilla::nsJNIString::nsJNIString] [@ dvmStringLen | JNI_CreateJavaVM | mozilla::nsJNIString::nsJNIString] [@ dvmAbort | dvmLookupClass]
Depends on: 748531
Resolution: DUPLICATE → ---
Based on comparing the call stack of the crash to the dalvik source code, it looks like dalvik is trying throw a dalvik.system.AllocationLimitError exception from dvmMalloc and while trying to load that class so that it can throw, it aborts. This seems to be a dalvik bug in an edge error case.
I filed http://code.google.com/p/android/issues/detail?id=32809 for this issue. There might be something we can do to avoid tickling this bug, like allocating less memory, but I would need STR for this before figuring out what we can do.
No recent crashes with this signature.
Status: REOPENED → RESOLVED
Closed: 12 years ago9 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.