Closed Bug 820458 Opened 12 years ago Closed 12 years ago

DOMWifiManager.js" line: 137 Assertion

Categories

(Core :: DOM: Device Interfaces, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla21
blocking-basecamp +
Tracking Status
firefox19 --- wontfix
firefox20 --- wontfix
firefox21 --- fixed
b2g18 --- fixed

People

(Reporter: dougt, Assigned: mrbkap)

Details

Attachments

(1 file)

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}]
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 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+
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?
blocking-basecamp: --- → +
Attachment #694391 - Flags: approval-mozilla-b2g18?
Marking FIXED as this is already on inbound and b2g18 (per b2g endgame rule).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: