709358 - crash libflashplayer

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Lawrence Mandel [:lmandel] (use needinfo)]

This bug was filed from the Socorro interface and is 
report bp-2904d2fd-be96-43a2-b8b2-dbf732111207 .
============================================================= 
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	libflashplayer.so 	libflashplayer.so@0x457bc0 	
1 	libflashplayer.so 	libflashplayer.so@0x4531c7 	
2 	dalvik-heap (deleted) 	dalvik-heap @0x52daa6 	
3 	libflashplayer.so 	libflashplayer.so@0x611112 	
4 	libxul.so 	PluginEventRunnable::Run 	dom/plugins/base/android/ANPEvent.cpp:56
5 	libxul.so 	mozilla::AndroidBridge::ExecuteNextRunnable 	widget/src/android/AndroidBridge.cpp:1064
6 	libxul.so 	Java_org_mozilla_gecko_GeckoAppShell_executeNextRunnable 	widget/src/android/AndroidJNI.cpp:208
7 	libmozutils.so 	Java_org_mozilla_gecko_GeckoAppShell_executeNextRunnable 	other-licenses/android/APKOpen.cpp:297
8 	libdvm.so 	dvmPlatformInvoke 	
9 	libdvm.so 	dvmCallJNIMethod_staticNoRef 	
10 	libdvm.so 	dvmAsmSisterStart 	
11 	libdvm.so 	dvmMterpStd 	
12 	libdvm.so 	dvmInterpret 	
13 	libdvm.so 	dvmInvokeMethod 	
14 	libdvm.so 	dvmFreeDexOrJar 	
15 	libdvm.so 	dvmAsmSisterStart 	
16 	libdvm.so 	dvmMterpStd 	
17 	libdvm.so 	dvmInterpret 	
18 	libdvm.so 	dvmCallMethodV 	
19 	libdvm.so 	JNI_CreateJavaVM 	
20 	libandroid_runtime.so 	libandroid_runtime.so@0x3c303 	
21 	libandroid_runtime.so 	libandroid_runtime.so@0x3de0d 	
22 	dalvik-LinearAlloc (deleted) 	dalvik-LinearAlloc @0x724f6 	
23 	dalvik-heap (deleted) 	dalvik-heap @0x40e36 	
24 	libcutils.so 	property_get 	
25 	libcutils.so 	set_process_name 	
26 	app_process 	app_process@0xccb 	
27 	app_process 	app_process@0x1026 	
28 	libandroid_runtime.so 	libandroid_runtime.so@0xd2766 	
29 	app_process 	app_process@0xb32 	
30 	app_process 	app_process@0xb32 	
31 	libc.so 	__libc_init 	
32 		@0xffffffe2 	
33 	app_process 	app_process@0x32 	
34 	app_process 	app_process@0xb1e

Comment 1

[Scoobidiver (away)]

Which version of Flash did you use?

Comment 2

[Lawrence Mandel [:lmandel] (use needinfo)]

My phone shows that I have Adobe Flash Player 10.1.105.333 installed.

Comment 3

[Scoobidiver (away)]

Try to update to Flash 11.1.112.60, which is the latest version:
http://kb2.adobe.com/cps/923/cpsid_92359.html

Comment 4

[Lawrence Mandel [:lmandel] (use needinfo)]

Updating Flash is not an option for all mobile users. For ex., I can't update flash on my HTC Desire as I do not have enough space for the Flash 11 runtime. My expectation is that a problem with Flash will not cause Firefox to crash. Can't we isolate Flash so that it doesn't crash the browser?

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

Meant to add that I will update Flash on my Samsung Galaxy S II and report back if I have any further crashes.

Comment 6

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Lawrence Mandel [:lmandel] from comment #4)
> Updating Flash is not an option for all mobile users. For ex., I can't
> update flash on my HTC Desire as I do not have enough space for the Flash 11
> runtime. My expectation is that a problem with Flash will not cause Firefox
> to crash. Can't we isolate Flash so that it doesn't crash the browser?

No, we can not isolate Flash on Android. Flash on Android is inherently an "in-process" model. When Flash goes down, we go down too. Session restore will help mitigate the situation, but not the crash.

Comment 7

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Mark Finkle (:mfinkle) from comment #6)
> (In reply to Lawrence Mandel [:lmandel] from comment #4)
> > Updating Flash is not an option for all mobile users. For ex., I can't
> > update flash on my HTC Desire as I do not have enough space for the Flash 11
> > runtime. My expectation is that a problem with Flash will not cause Firefox
> > to crash. Can't we isolate Flash so that it doesn't crash the browser?
> 
> No, we can not isolate Flash on Android. Flash on Android is inherently an
> "in-process" model. When Flash goes down, we go down too. Session restore
> will help mitigate the situation, but not the crash.

Well, that's disappointing but I guess it's a path we've chosen by supporting Flash on mobile (which is working pretty well I might add). 

I'm putting this in the won't fix state as, from Mark's comment 6, we can't fix this issue.

Comment 8

[Scoobidiver (away)]

(In reply to Mark Finkle (:mfinkle) from comment #6)
> When Flash goes down, we go down too.
For the record, 20% of crashes in 11.0a1 are caused by Flash.