Closed Bug 1230522 Opened 5 years ago Closed 5 years ago

crash in java.lang.UnsupportedOperationException: JNI Function called before it was loaded at org.mozilla.gecko.gfx.NativePanZoomController.getOverScrollMode(Native Method)

Categories

(Firefox for Android :: General, defect)

ARM
Android
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Firefox 45
Tracking Status
firefox45 --- fixed
fennec 45+ ---

People

(Reporter: wgianopoulos, Assigned: kats)

References

Details

(Keywords: crash, topcrash-android-armv7)

Crash Data

Attachments

(2 files)

This bug was filed from the Socorro interface and is 
report bp-b252670b-b0db-4073-906c-1804f2151202.
=============================================================
For the past couple of days, I have been getting this crash often upon launch8ing the browser.

I have only had this occur on my Samsung Galaxy tab 2 7.0.  I do not get this issue on my nexus 7 2012.
OS: Unspecified → Android
Hardware: Unspecified → ARM
Version: unspecified → Trunk
Blocks: 1206872
tracking-fennec: --- → ?
Assignee: nobody → bugmail.mozilla
From the crash-stats there's also a lot of crashes with the signature java.lang.UnsupportedOperationException: JNI Function called before it was loaded at org.mozilla.gecko.gfx.NativePanZoomController.handleTouchEvent(Native Method) 

Both of these are happening because native functions are getting called in NativePanZoomController before libxul is loaded, and the function implementations are actually available. We should avoid doing those calls. I'll cook up some patches for this.
These don't need to be native right now. Maybe not ever.
Attachment #8697394 - Flags: review?(rbarker)
Attachment #8697394 - Flags: review?(rbarker) → review+
Attachment #8697397 - Flags: review?(rbarker) → review+
https://hg.mozilla.org/mozilla-central/rev/6fb0e753c32b
https://hg.mozilla.org/mozilla-central/rev/2bf33b959e6d
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 45
Blocks: 1231915
tracking-fennec: ? → 45+
You need to log in before you can comment on or make changes to this bug.