1235246 - crash in java.lang.NullPointerException: Null native pointer at org.mozilla.gecko.mozglue.GeckoLoader.nativeRun(Native Method)

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Bill Gianopoulos [:WG9s]]

This bug was filed from the Socorro interface and is 
report bp-a4640ba0-0617-42fc-a2e5-6bf542151227.
=============================================================

Comment 1

[(inactive) Jim Chen [:jchen] [:darchons]]

Attachment: Always execute a queued call if it's overdue (v1)

GeckoThread.queueNativeCallLocked tries to execute a queued native call
if it's already overdue, but it incorrectly checked that the queue is
not empty. That check is not necessary, and an overdue native call
should always be executed. One-line patch, r=me.

Comment 2

[(inactive) Jim Chen [:jchen] [:darchons]]

Attachment: Only prioritize compositor events in GLController (v1)

Only three GLController events -- CreateCompositor, PauseCompositor, and
OnResumedCompositor should be prioritized through GLControllerEvent. The
other GLController events should follow the normal event queue ordering
to prevent race conditions.

Comment 3

[(inactive) Jim Chen [:jchen] [:darchons]]

Attachment: Configure GeckoLayerClient after GLController is initialized (v1)

LayerView used to call GeckoLayerClient.onGeckoReady directly if Gecko
is sufficiently loaded. However, onGeckoReady indirectly calls
GLController.createCompositor, and it's possible for the
createCompositor event to be prioritized so that it happens before we
initialize GLController, causing a crash. This patch moves the
onGeckoReady call to the Gecko thread, after GLController is
initialized, to avoid this race condition.

Comment 4

[Bill Gianopoulos [:WG9s]]

I am not sure why I always find things like this over Holidays.  Sorry for that. I know it takes longer to fix them. But then, but then I do have this antiquated old Samsung Galaxy Tab 2 that I am using that is slower than anything else so seems to find these kind of odd race conditions.

Comment 5

[(inactive) Jim Chen [:jchen] [:darchons]]

(In reply to Bill Gianopoulos [:WG9s] from comment #4)
> I am not sure why I always find things like this over Holidays.  Sorry for
> that. I know it takes longer to fix them. But then, but then I do have this
> antiquated old Samsung Galaxy Tab 2 that I am using that is slower than
> anything else so seems to find these kind of odd race conditions.

No, it's good that you found it! I'm sure a lot of users are encountering it based on the crash volume.

Comment 6

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/014d0b989ace
https://hg.mozilla.org/integration/mozilla-inbound/rev/bd5bcf200648
https://hg.mozilla.org/integration/mozilla-inbound/rev/6691a39fbeb8

Comment 7

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/014d0b989ace
https://hg.mozilla.org/mozilla-central/rev/bd5bcf200648
https://hg.mozilla.org/mozilla-central/rev/6691a39fbeb8

Comment 8

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

Jim - This crash is #8 on Fx44b8. Should we be uplifting this?

Comment 9

[(inactive) Jim Chen [:jchen] [:darchons]]

Not this particular bug but I think bug 1236643 will help (different bug but same crash signature)