1196299 - crash in java.lang.UnsatisfiedLinkError: at java.lang.Runtime.loadLibrary(Runtime.java) mostly on Kindle Tablets

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: General, defect)

Description

[Kevin Brosnan [Ex-Mozilla]]

This bug was filed from the Socorro interface and is 
report bp-00a5a0e8-cf95-4f7e-b9d1-0edeb2150817.
=============================================================

java.lang.UnsatisfiedLinkError: Couldn't load mozglue from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/org.mozilla.firefox_beta-1.apk"],nativeLibraryDirectories=[/data/app-lib/org.mozilla.firefox_beta-1, /vendor/lib, /system/lib]]]: findLibrary returned null
	at java.lang.Runtime.loadLibrary(Runtime.java:358)
	at java.lang.System.loadLibrary(System.java:526)
	at org.mozilla.gecko.mozglue.GeckoLoader.doLoadLibraryExpected(GeckoLoader.java:423)
	at org.mozilla.gecko.mozglue.GeckoLoader.doLoadLibrary(GeckoLoader.java:454)
	at org.mozilla.gecko.mozglue.GeckoLoader.loadMozGlue(GeckoLoader.java:517)
	at org.mozilla.gecko.GeckoThread.initGeckoEnvironment(GeckoThread.java:93)
	at org.mozilla.gecko.GeckoThread.run(GeckoThread.java:169

This is the number one top crash in beta with 15% of crashes.

Manufacturer  Model
Amazon  KFTHWI
Amazon  KFSOWI
Nokia   NokiaX2DS
samsung GT-I9300
samsung GT-I9060I
samsung GT-S7582
alps    mn84l_8039_20203
Amazon  KFAPWA

Snorp would you assing this out? While most of the crashes are on Amazon hardware there are a number of normal Android devices reporting this as well which concerns me.

Comment 1

[James Willcox (:snorp) ([e-mail]) (he/him)]

Kevin do we have logcats for any of these crashes? I'm not sure if we even collect those for Java crashes...

Comment 2

[James Willcox (:snorp) ([e-mail]) (he/him)]

This stack trace is odd. It should not be possible for GeckoLoader.doLoadLibraryExpected() to throw an exception, since it catches everything.

Comment 3

[James Willcox (:snorp) ([e-mail]) (he/him)]

We rethrow the original exception and report that, so the stack makes sense.

Jim found me some logcats and it looks like these devices are running an x86 apk on an ARM device. From the logcat:

08-15 02:43:38.910 6717 6742 E GeckoLoader: Load diagnostics: LOAD mozglue: ABI: x86-gcc3, armeabi-v7a: Data: /data/data/org.mozilla.firefox_beta, ax=false, ddx=false, -1x=false, -2x=false, nativeLib: /data/app-lib/org.mozilla.firefox_beta-1, dirx=true, libx=false

The important bit there is the 'ABI: x86-gcc3, armeabi-v7a', which points to a mismatch. So...did something get hosed up with the deployment to Play?

Comment 4

[Kevin Brosnan [Ex-Mozilla]]

So resolved invalid?

Comment 5

[Kevin Brosnan [Ex-Mozilla]]

See bug 1119915 for providing a way to alert users to the mistake.

Comment 6

[James Willcox (:snorp) ([e-mail]) (he/him)]

(In reply to Kevin Brosnan [:kbrosnan] from comment #4)
> So resolved invalid?

I think so, unless releng had a problem. The versions and stuff look alright on the Play console, though.

Comment 7

[Robert Kaiser]

(In reply to Kevin Brosnan [:kbrosnan] from comment #5)
> See bug 1119915 for providing a way to alert users to the mistake.

Actually, bug 1222925 is the ABI mismatch alert.