Delay WMF system DLL loading
Categories
(Core :: Audio/Video, enhancement)
Tracking
()
People
(Reporter: emmamalysz, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxperf])
Attachments
(1 file)
(deleted),
application/x-7z-compressed
|
Details |
Right now, the following DLLs are loaded during startup: https://searchfox.org/mozilla-central/source/dom/media/platforms/wmf/WMFUtils.cpp#171-176. In the attached profile, these reads took over a second during a cold startup on an HDD device. If they are not necessary for startup, let's see if we can delay loading these system DLLs to improve Disk I/O.
Comment 1•4 years ago
|
||
Jean-Yves, is it feasible / do you know what it would take to defer running wmf::MFStartup()
until after startup, and maybe just lazily initialize it if we're in a startup path that needs it? It feels like something which would not commonly be needed for about:home or a typical page loaded on startup, and its DLLs do seem to represent a nontrivial chunk of startup IO.
Comment 2•4 years ago
|
||
(In reply to Doug Thayer [:dthayer] from comment #1)
Jean-Yves, is it feasible / do you know what it would take to defer running
wmf::MFStartup()
until after startup, and maybe just lazily initialize it if we're in a startup path that needs it? It feels like something which would not commonly be needed for about:home or a typical page loaded on startup, and its DLLs do seem to represent a nontrivial chunk of startup IO.
Problem is that on startup we check HW acceleration support ; this is done very early on and require the DLL to be loaded.
However, what you are trying to achieve will be accomplished once bug 1595994 is completed.
It's really the only way to go about it that won't slow down all content processes.
I'll mark this bug as duplicate of that bug, as that's one of the aim (along many others)
Description
•