Closed Bug 708283 Opened 13 years ago Closed 13 years ago

NullPointerException in VideoPlayer on launch


(Firefox for Android Graveyard :: General, defect)

Firefox 9
Not set


(firefox8 unaffected, firefox9 fixed, firefox10 fixed, firefox11 fixed)

Firefox 11
Tracking Status
firefox8 --- unaffected
firefox9 --- fixed
firefox10 --- fixed
firefox11 --- fixed


(Reporter: gcp, Assigned: blassey)



(Keywords: crash, Whiteboard: [mobile-crash][inbound])


(1 file)

Happens whenever I try to launch.

    E/AndroidRuntime(17631): FATAL EXCEPTION: main
    E/AndroidRuntime(17631): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.mozilla.fennec_morbo/org.mozilla.gecko.VideoPlayer}: java.lang.NullPointerException
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        at$1500(
    E/AndroidRuntime(17631):        at$H.handleMessage(
    E/AndroidRuntime(17631):        at android.os.Handler.dispatchMessage(
    E/AndroidRuntime(17631):        at android.os.Looper.loop(
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        at java.lang.reflect.Method.invokeNative(Native Method)
    E/AndroidRuntime(17631):        at java.lang.reflect.Method.invoke(
    E/AndroidRuntime(17631):        at$
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        at dalvik.system.NativeStart.main(Native Method)
    E/AndroidRuntime(17631): Caused by: java.lang.NullPointerException
    E/AndroidRuntime(17631):        at org.mozilla.gecko.VideoPlayer.onCreate(
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        at
    E/AndroidRuntime(17631):        ... 11 more
    W/ActivityManager( 2715):   Force finishing activity org.mozilla.fennec_morbo/org.mozilla.gecko.VideoPlayer
    I/dumpstate(17640): begin
Attached patch patchSplinter Review
I confirm this fixes the issue for me.
Product: Fennec Native → Fennec
Target Milestone: --- → Firefox 9
Version: unspecified → Firefox 9
More info: this is a Samsung Galaxy S2 with the stock Samsung firmware. Fresh compile and install of Fennec.
Blocks: 705572
Attachment #579725 - Flags: review?(doug.turner)
Attachment #579725 - Flags: review?(doug.turner) → review+
i can't reproduce this crash on samsung galaxy S2, Fx9 beta 5 build.  Running a clean profile, i can open firefox, visit a youtube page, and launch the youtube player and play videos.  no crash.

gcp, can you share more details on your repro steps so i can reproduce?
Not sure why version was set to 9 here? This was a XUL build from (approximately):

There are no steps to reproduce, the crash is immediately after launch.
Target Milestone: Firefox 9 → ---
Version: Firefox 9 → Trunk
Attachment #579725 - Flags: approval-mozilla-beta?
Attachment #579725 - Flags: approval-mozilla-aurora?
Keywords: crash, reproducible
Whiteboard: [mobile-crash]
pushed to inbound
Whiteboard: [mobile-crash] → [mobile-crash][inbound]
Naoki, why did you mark this as reproducible? Have you been able to reproduce it?
I think I marked this bug reproducible by mistake.  I was looking at multiple crashing bugs during this time.
Keywords: reproducible
Is it clear that beta is affected at this point?
(In reply to Alex Keybl [:akeybl] from comment #9)
> Is it clear that beta is affected at this point?


A second shortcut is created on installation Firefox Beta, which when invoked causes this NPE.
Assignee: nobody → blassey.bugs
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 11
Version: Trunk → Firefox 9
Blocks: 708574
Comment on attachment 579725 [details] [diff] [review]

[Triage Comment]
We've now had a reproduction in 708574. Please land on aurora and beta. We'll be re-spinning beta 5 mobile this morning for this bug. Please make sure to land on the beta 5 branch of beta, as well as default/tip. Thanks!
Attachment #579725 - Flags: approval-mozilla-beta?
Attachment #579725 - Flags: approval-mozilla-beta+
Attachment #579725 - Flags: approval-mozilla-aurora?
Attachment #579725 - Flags: approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.