1318074 - Crash in java.lang.NullPointerException: at org.mozilla.gecko.MediaPlayerManager.onCreate(MediaPlayerManager.java)

Status: RESOLVED DUPLICATE of bug 1319173

(Firefox for Android Graveyard :: General, defect, P1)

Description

[Marcia Knous [:marcia]]

This bug was filed from the Socorro interface and is 
report bp-5c207176-0b9f-4834-9db4-1ee422161116.
=============================================================

New crash seen on trunk: http://bit.ly/2fW7u4V. Crashes started using the 20161115060313 build. Looks as if it affects some Nexus handsets including the 5x, which has the highest percentage of crashes.

Comment 1

[Alex Thompson]

I'm affected by this crash (Nightly, Nexus 5X, Android 7.0, N5D91L). The crash occurs after nightly is in the background and I switch back to it either using the app switcher or a shortcut on the desktop. This step cannot be reliably reproduced and I don't yet understand the conditions to put it in this state. After crashing, the crash report loads. Selecting either "Restart Firefox" or "Close" results in another crash. The only way to recover from this crash loop is to close nightly and the crash reporter by swiping them away in the app switcher.

Comment 2

[Ioana Chiorean]

I get this all the time - with and without sync after a few minutes I use nightly
https://crash-stats.mozilla.com/report/index/81193f3c-d131-45b4-8b8a-75d512161121

Crash reporter broken reported in Bug 1318204 ( because of bug 1301655 )

Comment 3

[Julian Chu [:walkingice]]

I am watching this bug.

The easiest way I reproduce is to simulate Activity be destroyed due to low memory.

Go to Android Setting, enable and enter developer options. enable "Don't keep activities", then each activities will be killed once it goes to background.

launch Fennec, open another activity such as Settings, then press back key.

Comment 4

[Julian Chu [:walkingice]]

I think we can register listener to later callback such as onCreateView as a workaround, to make sure the view already exists. Will it cause any problem if we don't register callback in onCreate?

Comment 5

[Sebastian Kaspari (:sebastian; :pocmo)]

This looks a lot like it is the same issue than bug 1319173 (has already r+'ed patch)

Comment 6

[Julian Chu [:walkingice]]

yes, I think this one is duplicated.

Comment 7

[Wellington Torrejais da Silva]

The problem still on latest nightly build for Android

Comment 8

[Sebastian Kaspari (:sebastian; :pocmo)]

This should be fixed in Nightly >= 2016-11-23. And I can't reproduce this with the steps from comment 3 anymore. Do you still see it in the latest builds and do you have steps to reproduce this crash?