Open Bug 1627086 Opened 7 months ago Updated 5 months ago

Init safe browsing later during startup

Categories

(Toolkit :: Safe Browsing, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: dthayer, Assigned: emalysz)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [fxperf:p3])

Attachments

(1 file)

We read around 7MB from the goog-phish-proto.vlpset file during startup, before about:home has finished loading. It seems like this could be pushed back.

Marking fxperf:p3 for now because I'm not sure we could push this back much (I would guess we need it as close as possible to the first network request), so I'm not sure we could gain much.

I think it's initialized at https://searchfox.org/mozilla-central/rev/4d2a9d5dc8f0e65807ee66e2b04c64596c643b7a/browser/components/BrowserGlue.jsm#2073-2080 and there's a comment there saying it needs to be initialized early-ish.

I could be convinced it's higher priority though, especially if you have an idea of where/when we could initialize this instead.

Whiteboard: [fxperf] → [fxperf:p3]

It would need to happen at the same time as it currently does if we're not just loading about:home. But if we are, it would ideally happen once we know about:home has settled. I believe we know about:home has settled around the time we record this timestamp. It would be a bit awkward including it there, but that's about where in the timeline I think it should go. We should also race against that with a callback in _scheduleArbitrarilyLateIdleTasks in case about:home never settles for some reason.

Priority: -- → P3
Assignee: nobody → emalysz
See Also: → 1635575
Depends on: 1637024
You need to log in before you can comment on or make changes to this bug.