Bug 1089405 - Move SettingsRequestManager load to near top of b2g boot process r=fabrice.

SettingsRequestManager is responsible for bootstrapping the settings api
without this near the top of the boot process any consumers before race
to aquire locks/get settings.
This commit is contained in:
James Lal 2014-10-27 15:21:01 -07:00
parent ccfa913be6
commit f5f5ecde02
2 changed files with 5 additions and 1 deletions

View File

@ -11,6 +11,11 @@ const Ci = Components.interfaces;
const Cu = Components.utils;
const Cr = Components.results;
// The load order is important here SettingsRequestManager _must_ be loaded
// prior to using SettingsListener otherwise there is a race in acquiring the
// lock and fulfilling it. If we ever move SettingsListener or this file down in
// the load order of shell.html things will likely break.
Cu.import('resource://gre/modules/SettingsRequestManager.jsm');
Cu.import('resource://gre/modules/XPCOMUtils.jsm');
Cu.import('resource://gre/modules/Services.jsm');

View File

@ -5,7 +5,6 @@
* You can obtain one at http://mozilla.org/MPL/2.0/. */
Cu.import('resource://gre/modules/ContactService.jsm');
Cu.import('resource://gre/modules/SettingsRequestManager.jsm');
Cu.import('resource://gre/modules/DataStoreChangeNotifier.jsm');
Cu.import('resource://gre/modules/AlarmService.jsm');
Cu.import('resource://gre/modules/ActivitiesService.jsm');