Closed
Bug 1103410
Opened 9 years ago
Closed 8 years ago
crash in java.lang.RuntimeException: Unhandled error for GeckoRequest FindInPage:Find: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import] JS stack:
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec+)
RESOLVED
FIXED
Firefox 37
Tracking | Status | |
---|---|---|
fennec | + | --- |
People
(Reporter: aaronmt, Assigned: capella)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file, 1 obsolete file)
2.24 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is report bp-c18cf218-cb11-4da0-afec-806db2141121. ============================================================= java.lang.RuntimeException: Unhandled error for GeckoRequest FindInPage:Find: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import] JS stack: get_finder@chrome://global/content/bindings/browser.xml:360:25 FindHelper._init@chrome://browser/content/FindHelper.js:58:4 FindHelper.doFind@chrome://browser/content/FindHelper.js:104:6 FindHelper._findOpened/<@chrome://browser/content/FindHelper.js:36:6 requestHandler.observe<@resource://gre/modules/Messaging.jsm:147:27 TaskImpl_run@resource://gre/modules/Task.jsm:314:39 TaskImpl@resource://gre/modules/Task.jsm:275:2 createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:249:13 at org.mozilla.gecko.util.GeckoRequest.onError(GeckoRequest.java:92) at org.mozilla.gecko.GeckoAppShell$3.handleMessage(GeckoAppShell.java:438) at org.mozilla.gecko.EventDispatcher.dispatchEvent(EventDispatcher.java:166) at org.mozilla.gecko.GeckoAppShell.handleGeckoMessage(GeckoAppShell.java:2265) at org.mozilla.gecko.mozglue.GeckoLoader.nativeRun(Native Method) at org.mozilla.gecko.mozglue.GeckoLoader.nativeRun(Native Method) at org.mozilla.gecko.mozglue.GeckoLoader.nativeRun(Native Method) at org.mozilla.gecko.GeckoAppShell.runGecko(GeckoAppShell.java:371) at org.mozilla.gecko.GeckoThread.run(GeckoThread.java:190)
Reporter | ||
Updated•9 years ago
|
tracking-fennec: --- → ?
Assignee | ||
Comment 2•9 years ago
|
||
bug 1089655 ... looks like I mucked up the method signature completely :-/
Assignee: nobody → markcapella
Status: NEW → ASSIGNED
Flags: needinfo?(markcapella)
Attachment #8528024 -
Flags: review?(wjohnston)
Comment 3•8 years ago
|
||
Comment on attachment 8528024 [details] [diff] [review] bug1103410.diff Review of attachment 8528024 [details] [diff] [review]: ----------------------------------------------------------------- Ooh. Good catch. We should fix this. But we should also try to catch this closer to the error. I think this line right here is throwing: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/FindHelper.js#58 Can we wrap this JS in a try-catch and log something to the console there when this happens? We probably need to do something smarter in FindHelper.js to handle the error.
Attachment #8528024 -
Flags: review?(wjohnston) → review+
Comment 4•8 years ago
|
||
Do we need to dig in a bit more to see "why" browser.finder is failing?
tracking-fennec: ? → +
Assignee | ||
Comment 5•8 years ago
|
||
New patch as suggested by wesj ... whichs avoids the java crash, and moves the logging closer to the actual point of error, which we see extremely rarely, involving receipt of: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import] while trying to load module Finder.jsm http://mxr.mozilla.org/mozilla-central/source/toolkit/content/widgets/browser.xml?rev=8c589a6d637e&mark=360-360#354 I've been doing monkey testing and cannot duplicate this to trap it. It's been suggested that I chat with gabor, who by way of introduction I'll ni? in here. mfinkle, let me know if you think of another line of attack ?
Attachment #8528024 -
Attachment is obsolete: true
Flags: needinfo?(gkrizsanits)
Comment 6•8 years ago
|
||
Comment on attachment 8539126 [details] [diff] [review] bug1103410.diff This looks OK for now. If we continue to see this particular problem, we can work on a different, more specific fix.
Attachment #8539126 -
Flags: review+
Assignee | ||
Comment 7•8 years ago
|
||
push to try https://tbpl.mozilla.org/?tree=Try&rev=d464f20bc051 Also, note bug 1113698 comment #2 ... error manifests slightly differently, both involving failures of Gecko/Components, but theoretically could be triggered by matching user case involving a phone device and Find In Page actions.
Assignee | ||
Comment 8•8 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/0ff1c9cd9d15
Comment 9•8 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0ff1c9cd9d15
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(gkrizsanits)
Updated•2 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
•