Closed Bug 672786 Opened 13 years ago Closed 5 years ago

crash [@ mozilla::AndroidBridge::ValidateBitmap]

Categories

(Firefox for Android Graveyard :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: mfinkle, Unassigned)

References

Details

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

Crash Data

This bug was filed from the Socorro interface and is 
report bp-b8e23e2f-97a1-479a-870b-e477a2110719 .
============================================================= 


0 	libdvm.so 	libdvm.so@0x4325a 	
1 	libandroid_runtime.so 	libandroid_runtime.so@0x34ea6 	
2 	libandroid_runtime.so 	libandroid_runtime.so@0x56708 	
3 	libjnigraphics.so 	libjnigraphics.so@0x580 	
4 	libjnigraphics.so 	libjnigraphics.so@0x560 	
5 	libxul.so 	mozilla::AndroidBridge::ValidateBitmap 	widget/src/android/AndroidBridge.cpp:944
6 	libxul.so 	nsWindow::OnDraw 	widget/src/android/nsWindow.cpp:997
7 	libxul.so 	nsWindow::OnGlobalAndroidEvent 	widget/src/android/nsWindow.cpp:830
8 	libxul.so 	nsAppShell::ProcessNextNativeEvent 	widget/src/android/nsAppShell.cpp:389
9 	libxul.so 	nsBaseAppShell::DoProcessNextNativeEvent 	widget/src/xpwidgets/nsBaseAppShell.cpp:172
10 	libxul.so 	nsBaseAppShell::OnProcessNextEvent 	widget/src/xpwidgets/nsBaseAppShell.cpp:324
11 	libxul.so 	mozilla::dom::ContentParent::OnProcessNextEvent 	dom/ipc/ContentParent.cpp:999
12 	libxul.so 	nsThread::ProcessNextEvent 	nsTArray.h:140
13 	libxul.so 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:245
14 	libxul.so 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:111
15 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:219
16 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:511
17 	libxul.so 	nsBaseAppShell::Run 	widget/src/xpwidgets/nsBaseAppShell.cpp:191
18 	libxul.so 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:223
19 	libxul.so 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3572
20 	libxul.so 	Java_org_mozilla_gecko_GeckoAppShell_nativeRun 	toolkit/xre/nsAndroidStartup.cpp:132
21 	libmozutils.so 	Java_org_mozilla_gecko_GeckoAppShell_nativeRun 	other-licenses/android/APKOpen.cpp:234
22 	libdvm.so 	libdvm.so@0x11e77 	
23 	dalvik-LinearAlloc (deleted) 	dalvik-LinearAlloc @0x1e83a3 	
24 	dalvik-heap (deleted) 	dalvik-heap @0x60d9e7 	
25 	libdvm.so 	libdvm.so@0x43722 	
26 	data@app@org.mozilla.fennec_aurora-1.apk@classes.dex 	data@app@org.mozilla.fennec_aurora-1.apk@classes.dex@0x10145 	
27 	libmozutils.so 	Java_org_mozilla_gecko_GeckoAppShell_nativeRun 	other-licenses/android/APKOpen.cpp:234
GetSoftwareDrawBitmap always returns a valid Bitmap, so I guess this must be the situation where it disappears in-between the application asking for it and it using it? Though this part is on the main thread, so is that even possible?

It would be good to see the values of the parameters going into ValidateBitmap, or instructions to reproduce this (if it's easily reproducable).
possible dup/related to bug 686457?
Whiteboard: [mobile-crash]
Crash Signature: [@ libdvm.so@0x4325a] [@ mozilla::AndroidBridge::ValidateBitmap] → [@ libdvm.so@0x4325a] [@ mozilla::AndroidBridge::ValidateBitmap] [@ libjnigraphics.so@0x6ee]
As libdvm.so has been added to the Socorro skiplist, I change the crash signature.

In addition, as some crashes with a signature containing libandroid_runtime.so have a similar stack trace, I add them.
Crash Signature: [@ libdvm.so@0x4325a] [@ mozilla::AndroidBridge::ValidateBitmap] [@ libjnigraphics.so@0x6ee] → libandroid_runtime.so@0x34bd9] [@ libandroid_runtime.so@0x364b5] [@ mozilla::AndroidBridge::ValidateBitmap] [@ libdvm.so@0x4325a] [@ libandroid_runtime.so@0x34ea6] [@ libandroid_runtime.so@0x3431d] [@ libandroid_runtime.so@0x36c25] [@ libandroid_run…
OS: Linux → Android
Hardware: All → ARM
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.