Open Bug 1490814 Opened 7 years ago Updated 3 years ago

{add,remove}BootstrappedManifestLocation() should not do extra work if there's no change

Categories

(Core :: XPCOM, enhancement, P3)

Product:
Core
Component:
XPCOM
Version:
60 Branch
Type:
enhancement

Tracking

()

People

(Reporter: aswan, Unassigned)

Details

I haven't dug in closely, but when I made an innocuous change to disable the Screenshots system addon, it caused a failure in browser/base/content/test/performance/browser_preferences_usage.js since we call Cm.removeBootstrappedManifestLocation() when disabling screenshots and that apparently did some re-computation that read the pref chrome.override_package.global a bunch of times. But, screenshots doesn't actually have a chrome.manifest, this should be detected and any unnecessary work to update/rebuild the registry should be skipped in this case.
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.