Closed Bug 1492963 Opened 5 years ago Closed 5 years ago

Stop doing storage initialization at startup

Categories

(WebExtensions :: General, enhancement)

Product:
WebExtensions
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Performance Impact:high, firefox64 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla64
Project Flags:
Performance Impact high
Tracking Flags:
Tracking Status
firefox64 --- fixed

People

(Reporter: kmag, Assigned: kmag)

References

Details

Attachments

(1 file)

Bug 1492963 - Avoid data migration and/or loading ContextualIdentityService right after extension startup. r?aswan!
46 bytes, text/x-phabricator-request
aswan
: review+
Details | Review 
The storage API is entirely async. There is absolutely no reason for us to do any of its initialization work on the startup path.
Whiteboard: [qf] → [qf:p1:f64]
Comment on attachment 9011219 [details]
Bug 1492963 - Avoid data migration and/or loading ContextualIdentityService right after extension startup. r?aswan!

Andrew Swan [:aswan] has approved the revision.
Attachment #9011219 - Flags: review+
Pushed by aswan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dee9b277dba7
Avoid data migration and/or loading ContextualIdentityService right after extension startup. r=aswan
https://hg.mozilla.org/mozilla-central/rev/dee9b277dba7
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox64: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Will this bug require manual testing? if so please specify some steps to validate or set the 'qe-verify-' flag, thank you
Flags: needinfo?(kmaglione+bmo)
Flags: needinfo?(kmaglione+bmo) → qe-verify-
Performance Impact: --- → P1
Whiteboard: [qf:p1:f64]
You need to log in before you can comment on or make changes to this bug.