1110840 - crash in java.lang.NullPointerException: at android.view.MenuInflater$MenuState.addItem(MenuInflater.java)

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Aaron Train [:aaronmt]]

This bug was filed from the Socorro interface and is 
report bp-215da35c-d37f-4c38-a3d5-15b5e2141211.
=============================================================

java.lang.NullPointerException
	at android.view.MenuInflater$MenuState.addItem(MenuInflater.java:451)
	at android.view.MenuInflater.parseMenu(MenuInflater.java:188)
	at android.view.MenuInflater.inflate(MenuInflater.java:110)
	at org.mozilla.gecko.GeckoApp.onCreateOptionsMenu(GeckoApp.java:325)
	at org.mozilla.gecko.BrowserApp.onCreateOptionsMenu(BrowserApp.java:2595)
	at android.app.Activity.onCreatePanelMenu(Activity.java:2526)
	at android.support.v4.app.FragmentActivity.onCreatePanelMenu(Unknown Source)
	at org.mozilla.gecko.GeckoApp.onCreatePanelMenu(GeckoApp.java:402)
	at org.mozilla.gecko.GeckoApp.getMenuPanel(GeckoApp.java:339)
	at org.mozilla.gecko.toolbar.BrowserToolbar.openOptionsMenu(BrowserToolbar.java:879)
	at org.mozilla.gecko.BrowserApp.openOptionsMenu(BrowserApp.java:2637)
	at org.mozilla.gecko.toolbar.BrowserToolbar$8.onClick(BrowserToolbar.java:352)
	at android.view.View.performClick(View.java:4293)
	at android.view.View$PerformClick.run(View.java:17535)
	at android.os.Handler.handleCallback(Handler.java:725)
	at android.os.Handler.dispatchMessage(Handler.java:92)
	at android.os.Looper.loop(Looper.java:153)
	at android.app.ActivityThread.main(ActivityThread.java:5299)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:511)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:833)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
	at dalvik.system.NativeStart.main(Native Method)

Comment 1

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

Not many crashes. The stack looks like the "3 dot" button is pressed, the menu is starting to inflate and BOOM. Given that the system MenuInflater is used and not the GeckoMenuInflater, this must be a Gingerbread OS.

In the reports, I see "HTC One M8" listed, but that device should be running Kitkat. Maybe this is caused by the using an API 9 build on API 11+ device? The build ID in a report is "20141231030205" but looking in the FTP folders, both api-9 [1] and api-11 [2] builds seem to have that build ID.

[1] http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014-12-31-03-02-05-mozilla-central-android-api-9/fennec-37.0a1.multi.android-arm.txt
[2] http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014-12-31-03-02-05-mozilla-central-android-api-11/fennec-37.0a1.multi.android-arm.txt

Comment 2

[Aaron Train [:aaronmt]]

#5 on 38 currently, seeing the LG G3 (4.4) take the top spot

Comment 3

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Mark Finkle (:mfinkle) from comment #1)
> In the reports, I see "HTC One M8" listed, but that device should be running
> Kitkat. Maybe this is caused by the using an API 9 build on API 11+ device?
> The build ID in a report is "20141231030205" but looking in the FTP folders,
> both api-9 [1] and api-11 [2] builds seem to have that build ID.

Same build ID? That seems like a bad practice - Richard, do you agree? (and file if you do!)

Comment 4

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

This looks like it can be related...

Comment 5

[Richard Newman [:rnewman]]

(In reply to Michael Comella (:mcomella) from comment #3)

> Same build ID? That seems like a bad practice - Richard, do you agree? (and
> file if you do!)

I think there are Good Reasons why they're the same build ID. For one thing, they're generated by the same push.

Anyway, go take a look at Bug 1119915 and friends. This shouldn't be an issue on Play.

Comment 6

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

^ Soft dep.

Comment 7

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

Let's see if this becomes a problem on Release builds. The escape hatch in bug 1119915 is the way forward.

Comment 8

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.