Closed
Bug 1216939
Opened 9 years ago
Closed 6 years ago
Don't import IndexedDBHelper.jsm and SettingsDB.jsm in preload.js
Categories
(Firefox OS Graveyard :: Performance, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cyu, Assigned: cyu)
Details
Attachments
(1 file)
1.57 KB,
patch
|
Details | Diff | Splinter Review |
IndexedDB is used through IPC in content processes. There's no need to load IndexedDBHelper.jsm and SettingsDB.jsm in preload.js.
Assignee | ||
Comment 1•9 years ago
|
||
Oops! Accidentally marked as security-sensitive. Need help to make this bug public.
Assignee | ||
Comment 2•9 years ago
|
||
Paul, would you help uncheck the security-sensitive flag? Thanks :)
Flags: needinfo?(ptheriault)
Group: b2g-core-security
Flags: needinfo?(ptheriault)
Assignee | ||
Comment 3•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=806d118836da
Assignee | ||
Comment 4•9 years ago
|
||
Assignee: nobody → cyu
Attachment #8677950 -
Flags: review?(fabrice)
Comment 5•9 years ago
|
||
SettingsDB.jsm is used by SettingsRequestManager.jsm which is then used by SettingsService.js And this service can be used in child process unless I missed something, so we still benefit from preloading SettingsDB.jsm no?
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to [:fabrice] Fabrice Desré from comment #5) > SettingsDB.jsm is used by SettingsRequestManager.jsm which is then used by > SettingsService.js > And this service can be used in child process unless I missed something, so > we still benefit from preloading SettingsDB.jsm no? SettingsRequestManager states that it only lives in the parent process: https://dxr.mozilla.org/mozilla-central/source/dom/settings/SettingsRequestManager.jsm#1219 so I don't think i has any benefit in loading it in child processes.
Comment 7•9 years ago
|
||
Hm, yes - but we still load it when using the SettingsService in child processes. Maybe we should not do that instead?
Assignee | ||
Comment 8•9 years ago
|
||
(In reply to [:fabrice] Fabrice Desré from comment #7) > Hm, yes - but we still load it when using the SettingsService in child > processes. Maybe we should not do that instead? We shouldn't. I think we should also have a check in SettingsService that don't import SettingsRequestManager.jsm in the child process. The JSM is loaded only to throw an exception.
Assignee | ||
Comment 9•9 years ago
|
||
After checking SettingsServiceLock, I think it only resides in the parent process because it has direct calls to SettingsRequestManager.
Updated•9 years ago
|
Priority: -- → P2
Updated•8 years ago
|
Attachment #8677950 -
Flags: review?(fabrice)
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•