handleGeckoMessage throws java.lang.NullPointerException on startup

RESOLVED FIXED

Status

()

Firefox for Android
General
P2
critical
RESOLVED FIXED
6 years ago
a year ago

People

(Reporter: dougt, Unassigned)

Tracking

({crash})

unspecified
crash
Points:
---

Firefox Tracking Flags

(firefox11 fixed, fennec11+)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Stack:

E/GeckoShell(23007): org.mozilla.gecko.GeckoApp.handleDocumentStart(GeckoApp.java:493)
E/GeckoShell(23007): org.mozilla.gecko.GeckoAppShell.handleGeckoMessage(GeckoAppShell.java:1609)
E/GeckoShell(23007): org.mozilla.gecko.GeckoAppShell.nativeRun(Native Method)
E/GeckoShell(23007): org.mozilla.gecko.GeckoAppShell.nativeRun(Native Method)
E/GeckoShell(23007): org.mozilla.gecko.GeckoAppShell.runGecko(GeckoAppShell.java:420)
E/GeckoShell(23007): org.mozilla.gecko.GeckoApp$1GeckoTask.doInBackground(GeckoApp.java:357)
E/GeckoShell(23007): org.mozilla.gecko.GeckoApp$1GeckoTask.doInBackground(GeckoApp.java:303)
E/GeckoShell(23007): android.os.AsyncTask$2.call(AsyncTask.java:185)
E/GeckoShell(23007): java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
E/GeckoShell(23007): java.util.concurrent.FutureTask.run(FutureTask.java:138)
E/GeckoShell(23007): java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
E/GeckoShell(23007): java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
E/GeckoShell(23007): java.lang.Thread.run(Thread.java:1019)
(Reporter)

Updated

6 years ago
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All

Updated

6 years ago
Severity: normal → critical
Keywords: crash
Created attachment 569102 [details] [diff] [review]
patch

The expection is raised because we're asking for a non existent tab.
We receive a "document start" before creating the first tab, which is probably what need to be really fixed.
Attachment #569102 - Flags: review?(doug.turner)
Sounds like this is the same kinda error we see on XUL fennec when the "about:blank" page of a new tab fires off an event of two.

Wonder if this _is_ the case and if so, could we stop sending the messaging in JS?
(Reporter)

Updated

6 years ago
Attachment #569102 - Flags: review?(doug.turner) → review+
pushed:
http://hg.mozilla.org/projects/birch/rev/1d37f263df5f
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
tracking-fennec: --- → 11+
status-firefox11: --- → fixed
You need to log in before you can comment on or make changes to this bug.