Closed Bug 1355248 Opened 8 years ago Closed 8 years ago

Be lazier about a few imports in LoginManagerContent.jsm

Categories

(Toolkit :: Password Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: mccr8, Assigned: mccr8)

References

Details

Attachments

(1 file)

This prevents loading InsecurePasswordUtils.jsm at startup.
Currently InsecurePasswordUtils.jsm is loaded both eagerly and lazily by LoginManagerContent.jsm, for some reason.
Comment on attachment 8857030 [details] Bug 1355248 - Don't eagerly import InsecurePasswordUtils.jsm in LoginManagerContent.jsm. https://reviewboard.mozilla.org/r/128922/#review131500 Thanks ::: toolkit/components/passwordmgr/LoginManagerContent.jsm:30 (Diff revision 1) > +XPCOMUtils.defineLazyModuleGetter(this, "PrivateBrowsingUtils", > + "resource://gre/modules/PrivateBrowsingUtils.jsm"); The guideline before was to not bothering using a lazy module getter if you know it will be imported shortly after the importer is loaded. For PrivateBrowsingUtils it gets used on every page load if pwmgr is on (it is by default) so this would only help people with pwmgr off assuming other modules don't import it eagerly (I think most do and is the reason why it's done eagerly here too). E10s changed which processes modules are imported in though so it's possible that it's not always imported already in the content process.
Attachment #8857030 - Flags: review?(MattN+bmo) → review+
That's a good point. I'll just remove that part of the patch. There's another place that loads it so I'm sure it will be around anyways.
Pushed by amccreight@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b9d7467de823 Don't eagerly import InsecurePasswordUtils.jsm in LoginManagerContent.jsm. r=MattN
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: