Closed
Bug 696683
Opened 13 years ago
Closed 13 years ago
handleGeckoMessage throws java.lang.NullPointerException on startup
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Firefox for Android Graveyard
General
Tracking
(firefox11 fixed, fennec11+)
RESOLVED
FIXED
People
(Reporter: dougt, Unassigned)
Details
(Keywords: crash)
Attachments
(1 file)
653 bytes,
patch
|
dougt
:
review+
|
Details | Diff | Splinter Review |
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•13 years ago
|
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All
Comment 1•13 years ago
|
||
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)
Comment 2•13 years ago
|
||
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•13 years ago
|
Attachment #569102 -
Flags: review?(doug.turner) → review+
Comment 3•13 years ago
|
||
pushed: http://hg.mozilla.org/projects/birch/rev/1d37f263df5f
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
tracking-fennec: --- → 11+
Updated•12 years ago
|
status-firefox11:
--- → fixed
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•