Closed
Bug 820458
Opened 12 years ago
Closed 12 years ago
DOMWifiManager.js" line: 137 Assertion
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: dougt, Assigned: mrbkap)
Details
Attachments
(1 file)
1.38 KB,
patch
|
vchang
:
review+
|
Details | Diff | Splinter Review |
I see this at startup on a otoro device running a build from today. Not sure if it is important or not. I/Gecko ( 106): WARNING: NS_ENSURE_TRUE(aRequest) failed: file /builds/mozilla-central/dom/base/DOMRequest.cpp, line 220 E/GeckoConsole( 106): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMRequestService.fireError]" {file: "jar:file:///system/b2g/omni.ja!/components/DOMWifiManager.js" line: 137}]
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 694391 [details] [diff] [review] Bug 820458 - Try harder to avoid notifying for the same request twice. This is pretty self-explanatory. Basically, there could have already been a request to scan when we ask to scan, causing us to receive scan results but have the original request to scan fail.
Attachment #694391 -
Flags: review?(vchang)
Comment 3•12 years ago
|
||
Comment on attachment 694391 [details] [diff] [review] Bug 820458 - Try harder to avoid notifying for the same request twice. Review of attachment 694391 [details] [diff] [review]: ----------------------------------------------------------------- This patch is really cool.
Attachment #694391 -
Flags: review?(vchang) → review+
Assignee | ||
Comment 4•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/44e32ae854d8
Assignee | ||
Comment 5•12 years ago
|
||
Comment on attachment 694391 [details] [diff] [review] Bug 820458 - Try harder to avoid notifying for the same request twice. [Approval Request Comment] User impact if declined: The API will behave oddly in certain cases. Testing completed: I've had this in my tree for a while. It's now on inbound. Risk to taking this patch (and alternatives if risky): Little to no risk.
Attachment #694391 -
Flags: approval-mozilla-b2g18?
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → +
Assignee | ||
Comment 6•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/44814eb603cc
status-b2g18:
--- → fixed
Assignee | ||
Updated•12 years ago
|
Attachment #694391 -
Flags: approval-mozilla-b2g18?
Comment 7•12 years ago
|
||
Marking FIXED as this is already on inbound and b2g18 (per b2g endgame rule).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 8•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/44e32ae854d8
Updated•11 years ago
|
status-firefox19:
--- → wontfix
status-firefox20:
--- → wontfix
status-firefox21:
--- → fixed
Target Milestone: --- → mozilla21
You need to log in
before you can comment on or make changes to this bug.
Description
•