alessandro Reporter
	Description • 6 years ago

User Agent: Mozilla/5.0 (Android 6.0.1; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0
Build ID: 20180613100557

Steps to reproduce:

when clicking this link 
https://click.mail.onedrive.com/?qs=754ba470d97cd0320a48f7c6969135ad4fc00d82abb0d0d33048b8104dd83b3294c9b6741abd3550ac64d281ac7e8cc369319fafdbaf9e4fcbfe2548b0baea86
 Firefox(both 62 and 63)crashes on my android device (cynogenmood 13,marshnallow) the report for the crash can be found at
https://crash-stats.mozilla.com/report/index/27739c72-0ce3-4410-83d5-bfc640180627
 the error seems to be java.lang.UnsatisfiedLinkError: No implementation found for void org.mozilla.gecko.GeckoEditableChild.onKeyEvent(int, int, int, int, int, long, int, int, int, boolean, android.view.KeyEvent) (tried Java_org_mozilla_gecko_GeckoEditableChild_onKeyEvent and Java_org_mozilla_gecko_GeckoEditableChild_onKeyEvent__IIIIIJIIIZLandroid_view_KeyEvent_2) at org.mozilla.gecko.GeckoEditableChild.onKeyEvent(Native Method)








Actual results:

onestly I don't have any hope left for Firefox on android
I reported that Firefox crashes on Facebook mobile at version 60 and issue has not been fixed BUT WHY? COME ON
developer we're not even able to reproduce the crash and after months I get a reply from the crash report that it was due to hardware acceleration.
is that hard to fix it ?
it s simply a shame Firefox is not reliable at all

	Marcia Knous [:marcia]
	Comment 1 • 6 years ago

Adding crash report and affected branches. Need to bucket it in a better component. Will take a look at the crash stack and see if I can put it in a better component.

	Marcia Knous [:marcia]
	Comment 2 • 6 years ago

It looks as if there are only 4 total crashes so far in this signature, a few on 61 and one on62. We had a similar bug in the 59 cycle (Bug 1425553). Changing component to Geckoview based on where that bug was.

	Chris Peterson [:cpeterson]
	Comment 3 • 6 years ago

low volume crash involving Xposed framework (de.robv.android.xposed.XposedBridge) so priority P5.

http://www.xposedandroid.com/

	Marcia Knous [:marcia]
	Comment 4 • 5 years ago

This signature has moved up into the #2 top spot in 64.0.1 Fennec crashes. Confirming the bug as well as adding the topcrash keyword. cpeterson - any ideas as to why this might have increased in prominence in 64?

	Chris Peterson [:cpeterson]
	Comment 5 • 5 years ago

(In reply to Marcia Knous [:marcia - needinfo? me] from comment #4)
> This signature has moved up into the #2 top spot in 64.0.1 Fennec crashes.
> Confirming the bug as well as adding the topcrash keyword. cpeterson - any
> ideas as to why this might have increased in prominence in 64?

I don't know. I looked at some recent crash reports and none of them had the Xposed framework mentioned in comment 3, so this could be a more general bug and not something we can blame on a third-party framework.

I only see one crash in 65 Nightly and none in 65 Beta or 66 Nightly, which suggests that either the crash was fixed in 65 Nightly or there is something about release channel users' device configurations that is more likely to crash than pre-release users'.

Bug 1425553 fixed a similar crash, so perhaps this bug can be fixed in a similar fashion. Tagging with [geckoview] to send to GV triage.

java.lang.UnsatisfiedLinkError
	at org.mozilla.gecko.GeckoEditableChild.onKeyEvent(Native Method)
	at org.mozilla.geckoview.GeckoEditable.onKeyEvent(GeckoEditable.java:165)
	at org.mozilla.geckoview.GeckoEditable.sendKeyEvent(GeckoEditable.java:944)
	at org.mozilla.geckoview.GeckoEditable.sendKeyEvent(GeckoEditable.java:913)
	at org.mozilla.geckoview.GeckoEditable$12.run(GeckoEditable.java:2112)
	at android.os.Handler.handleCallback(Handler.java:751)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6121)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:892)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:782)

	Kevin Brosnan [Ex-Mozilla]
	Comment 6 • 5 years ago

Around 25% of the crashes are from a set top box OEM named Amlogic. Looks like a lot of the devices are OEM/white label. One possibly useful comment says "Tapped a YouTube link in reddit app". A few comments suggests that the crash is random or on startup.

I also see a small handful of obvious emulated devices Genymotion, Samsung x86 and x86 Pixels. Some people are grabbing the aarch64 builds as well.

	Julien Cristau [:jcristau] (back April 22)
	Comment 7 • 5 years ago

65 doesn't seem to be affected?  Big volume on 64 though.

	alessandro Reporter
	Comment 8 • 5 years ago

on 66 nighlty on my phone bug is still present after all this time...

	Kevin Brosnan [Ex-Mozilla]
	Comment 9 • 5 years ago

Crashes with a usable logcat 

https://crash-stats.mozilla.com/rawdumps/c41ae05d-5f2c-44ed-9ba9-81cb70181219.json
https://crash-stats.mozilla.com/rawdumps/8c8fe022-d7a8-428c-b310-a19330181219.json

	James Willcox (:snorp) (jwillcox@mozilla.com) (he/him) Assignee
	Comment 10 • 5 years ago

I guess we just need to queue up the native call in GeckoEditableChild.