1144616 - Firefox 36.0.1 crashes on Android 4.1.1, tries to use android.os.UserManager

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Mark]

Attachment: adb logcat output on launching Firefox 36.0.2

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150306135716

Steps to reproduce:

Using an Archos GamePad which runs Android 4.1.1, install Firefox from Google Play. Versions 36.0.1 and 36.0.2 show the problem.
Launch Firefox.


Actual results:

There is a brief flash of white screen (sometimes the address bar is momentarily visible) then it exits back to the launcher.


Expected results:

Firefox should run and work properly, as it did with version 36.0.

The problem seems to be that Firefox 36.0.1/36.0.2 attempts to use the class android.os.UserManager. But that was first added in API level 17 (Android 4.2). Firefox should check the OS/API level and not use that class if <17.

adb logcat output attached.

Comment 1

[Aaron Train [:aaronmt]]

Don't believe that's related. The restricted profile code should be doing an API level check. Richard?

Comment 2

[Mark]

Attachment: adb logcat output on launching Firefox 36.0 (which does not crash)

I have attached adb logcat output on launching Firefox 36.0 (which works correctly), perhaps comparing the two logs might help?

Comment 3

[Richard Newman [:rnewman]]

I think this looks suspect:

I/fennec  ( 7645): XRE_main returned 1
D/GeckoAppShell( 7645): Killing via System.exit()
I/AndroidRuntime( 7645): VM exiting with result code 0, cleanup skipped.

Comment 4

[Aaron Train [:aaronmt]]

Reminds me of bug 968357, the user in that bug used TitaniumBackup to completely nuke a corrupted install

Comment 5

[Mira Lobontiu (Android QA)]

Hi,

Does this issue still reproduce?

Thanks!

Comment 6

[Mira Lobontiu (Android QA)]

Hello,

Due to the lack of additional info, I'll close this issue as Incomplete.
If the reporter (or anyone else) can provide more information, please feel free to reopen or comment on the issue, and we'll have a thorough look on it.


Thank you,