Closed Bug 1098220 Opened 7 years ago Closed 7 years ago

[Exception... "Component does not have requested interface [nsISettingsServiceCallback.handle]" in SettingsService.js

Categories

(Core :: DOM: Core & HTML, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla37

People

(Reporter: gerard-majax, Assigned: qdot)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file)

Saw this on some boot of device with master

> 06-01 02:42:12.869   224   224 I Gecko   : settings 'handle' callback threw an exception, dropping: [Exception... "Component does not have requested interface [nsISettingsServiceCallback.handle]"  nsresult: "0x80004002 (NS_NOINTERFACE)"  location: "JS frame :: jar:file:///system/b2g/omni.ja!/components/SettingsService.js :: callHandle :: line 184"  data: no]
Kyle, maybe it's harmless and it's just a setting being set without any callback handler?

What about checking in SettingsService.js' callHandle (and others) that we do have a |.handle| property defined before using it? Maybe adding a warning.

Leaving exception like this may lure people into thinking there's a bug.
Flags: needinfo?(kyle)
Seems like an easy enough fix, yeah.
Flags: needinfo?(kyle)
Assignee: nobody → kyle
Comment on attachment 8540256 [details] [diff] [review]
Patch 1 (v1) - Change dump statements to debug statements in SettingsService

Review of attachment 8540256 [details] [diff] [review]:
-----------------------------------------------------------------

I think we set debug to default to true, but the patch is fine for me. And it's trivial.
Attachment #8540256 - Flags: review?(lissyx+mozillians) → review+
Blocks: 1107982
Will update patch to check for validity of .handle, and only print if DEBUG && handle is valid.
https://hg.mozilla.org/mozilla-central/rev/0529b5dca28e
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla37
Whiteboard: [systemsfe]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.