Closed Bug 934007 Opened 11 years ago Closed 7 years ago

dom/settings/tests/test_settings_events.html | ###!!! ASSERTION: cannot save prefs from content process

Categories

(Core :: DOM: Device Interfaces, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jgriffin, Assigned: gwagner)

References

Details

dom/settings/tests/test_settings_events.html fail with the assertion:

15:44:03     INFO -  [Child 867] ###!!! ASSERTION: cannot save prefs from content process: 'Error', file ../../../../gecko/modules/libpref/src/Preferences.cpp, line 624

log: https://tbpl.mozilla.org/php/getParsedLog.php?id=29997193&tree=Cedar#error0
"cannot save prefs from content process"

It doesn't look like much has recently changed in libpref related to this assertion.

Gregor, is there something wrong with test_settings_events.html?
http://dxr.mozilla.org/mozilla-central/source/dom/settings/tests/test_settings_events.html
Assignee: nobody → anygregor
Flags: needinfo?(anygregor)
I'm quite doubtful that the test is at fault. It's hard to say what's triggering this, unfortunately, since the list at http://mxr.mozilla.org/mozilla-central/ident?i=SavePrefFile isn't small and the clearly-b2g-related ones don't look like culprits to me. The best solution might be to change the triggering assert to a warning.
Flags: needinfo?(anygregor)
Hm we might check the pref when we generate the mozSettings binging on the navigator object. I believe we access a pref there. Reuben knows where this code lives.
Nah, generated bindings only do a Preferences::GetBool("dom.mozSettings.enabled") check to see if the interfaces should be exposed, and this test doesn't even use navigator.mozSettings.
Right thats only a get. The only other option I could come up with is an observer that listens to this event. But also not very likely.
FxOS/Gonk has been removed from the codebase. Mass-invalidating FxOS related Device Interface bugs to clean up the component. 

If I incorrectly invalidated something, please let me know.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Bulk correction of resolution of B2G bugs to INCOMPLETE.
Resolution: INVALID → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.