If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Firefox for Android crashes shortly after starting it on Impression I10

NEW
Unassigned

Status

()

Firefox for Android
General
--
critical
5 years ago
a year ago

People

(Reporter: Mika Suomalainen, Unassigned)

Tracking

({crash})

15 Branch
ARM
Android
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [native-crash][startupcrash])

Attachments

(2 attachments)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1

Steps to reproduce:

I opened Firefox.


Actual results:

In 5-15 seconds Firefox window disappeared (looks like it crashed).


Expected results:

Firefox should have stayed open until I closed it.
(Reporter)

Comment 1

5 years ago
I'll send logcat log, after I get it out from that tablet.
(Reporter)

Comment 2

5 years ago
Created attachment 666186 [details]
Logcat log from crash

Updated

5 years ago
Severity: normal → critical
Keywords: crash
OS: Linux → Android
Hardware: x86_64 → ARM
Whiteboard: [native-crash][startupcrash]
Do you crash with Nightly (http://nightly.mozilla.org), or Firefox Beta (on Google Play)? Can you try this debug build, install it and run it and capture the same log (with more additional details)? http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/mozilla-central-android-debug/1348936343/fennec-18.0a1.en-US.android-arm.apk
(Reporter)

Comment 4

5 years ago
I crash with Firefox 15.0.1 from F-Droid which is probably the stable version, because F-Droid also has Firefox Beta.

Yes, I can download it.
(Reporter)

Comment 5

5 years ago
Created attachment 666289 [details]
Nightly crash alogcat log

After opening Nightly, nothing happens until I press something. Then I get message asking me to "Force close" or "wait". I selected "Force close".
(In reply to Mika Suomalainen from comment #5)
> Created attachment 666289 [details]
> Nightly crash alogcat log
> 
> After opening Nightly, nothing happens until I press something. Then I get
> message asking me to "Force close" or "wait". I selected "Force close".

Bug 706500.

Comment 7

5 years ago
Can you provide the crash ID (bp-...) from about:crashes for your initial issue from a working version (Beta, Aurora or Nightly)?
(Reporter)

Comment 8

5 years ago
There is no working version, so I cannot.
Right after Fennec starts in your debug nightly log I see plenty of VFY messages. Is this bad?


I/ActivityManager( 2131): Start proc org.mozilla.fennec for activity org.mozilla.fennec/.App: pid=9089 uid=10064 gids={3003, 1015, 1006}
E/dalvikvm( 9089): Could not find class 'android.os.StrictMode$ThreadPolicy$Builder', referenced from method org.mozilla.gecko.GeckoApp.enableStrictMode
W/dalvikvm( 9089): VFY: unable to resolve new-instance 154 (Landroid/os/StrictMode$ThreadPolicy$Builder;) in Lorg/mozilla/gecko/GeckoApp;
D/dalvikvm( 9089): VFY: replacing opcode 0x22 at 0x0007
D/dalvikvm( 9089): VFY: dead code 0x0009-002f in Lorg/mozilla/gecko/GeckoApp;.enableStrictMode ()V
I/dalvikvm( 9089): Could not find method android.view.ViewConfiguration.hasPermanentMenuKey, referenced from method org.mozilla.gecko.GeckoApp.hasPermanentMenuKey
W/dalvikvm( 9089): VFY: unable to resolve virtual method 829: Landroid/view/ViewConfiguration;.hasPermanentMenuKey ()Z
D/dalvikvm( 9089): VFY: replacing opcode 0x6e at 0x0014
D/dalvikvm( 9089): VFY: dead code 0x0017-0017 in Lorg/mozilla/gecko/GeckoApp;.hasPermanentMenuKey ()Z

Updated

5 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Mika, what version of Android are you running on your Impression i10?

Your log files suggest that Firefox is crashing because Android's android.os.StrictMode.ThreadPolicy.Builder class does not exist. That class was added in Android 2.3 (Gingerbread), but we shouldn't crash here because we specifically check the Android version before calling this code:

https://hg.mozilla.org/mozilla-central/file/63b393c1facc/mobile/android/base/GeckoApp.java#l1740

I found some reviews online that describe many app compatibility problems with Impression i10. Some even assert that the Impression i10 is not running Android 2.3.1 as the manufacturer claims. That assertion sounds outlandish, but it would explain the exceptions in your log files.
Should we consider blocklisting the Impression i10? We use many Gingerbread+ APIs and checking them all via reflection instead of Build.VERSION.SDK_INT does not seem practical.

Other reports of API compatibility problems with Impression i10:

* https://www.amazon.com/review/R34WF19PLWYITD
  "Leader international claims the android version is 2.3.1, well not according to the logs from the device."

* https://github.com/Zanshinmu/Wifi-Fixer/issues/11
  "The crash is caused by a framework method that should be there in Android 2.3.x not existing. The code that crashes actually checks API version and uses the appropriate method. ... It's not a "bug" so much as a violation of Android's API guarantee."
Not to mention that those screenshots posted showcasing the device are clearly Android 2.1
(Reporter)

Comment 13

5 years ago
Chris, 

Settings --> SystemInfo says "Android version 2.3.1".

There are many compatibility problems. I have complained about them at my homepage http://mkaysi.github.com/articles/complaining/ImpressionI10.html#application-compatibility . By the way, that Wifi-Fixer issue is also reported by me.

https://github.com/github/android/issues/238#issuecomment-9006410 also suggests that the device has broken Java.
(Reporter)

Comment 14

5 years ago
I took some screenshots. https://plus.google.com/photos/113787158024729598288/albums/5794652485055963953 I hope that they help determining which Android version is running.

I repeat that this is stock ROM.
You need to log in before you can comment on or make changes to this bug.