CRLite uses 25% of CPU once per minute
Categories
(Core :: Security: PSM, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox82 | --- | unaffected |
firefox83 | --- | unaffected |
firefox84 | --- | fixed |
firefox85 | --- | fixed |
People
(Reporter: bit, Assigned: keeler)
References
(Blocks 1 open bug)
Details
(Whiteboard: [psm-assigned])
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0
Steps to reproduce:
I was just using Firefox Nightly as usual. Last build, Windows 10 x64.
I noticed strange periodical CPU usage.
Actual results:
Once per minute Firefox was using 25% CPU for some time (see attached screenshot). I checked what it was doing. There was some I/O using, \AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\security_state\crlite.stash file in particular.
All is OK with new test profile.
Firefox Profiler results: https://share.firefox.dev/3f697LF
Expected results:
There should not be this unusual CPU usage.
Assignee | ||
Comment 2•4 years ago
|
||
This patch uses nsICertStorage.hasPriorData() and a new local field on the
CRLite filter Remote Settings collection to avoid re-downloading and
re-processing CRLite filters and stashes that have already been put into
cert_storage.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
It's permanent now.
This is the latest build at the moment, 20201119095716.
Pushed by dkeeler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c1fe88096bb3 avoid re-downloading and re-processing CRLite filters/stashes that are already in cert_storage r=bbeurdouche
Comment 5•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
Will this be backported to Firefox 84?
Reducing CPU usage might be especially important especially with recent Chrome blog posts like https://blog.chromium.org/2020/11/tab-throttling-and-more-performance.html.
Assignee | ||
Comment 7•4 years ago
|
||
Yes - this isn't enabled in release yet, but it will affect early betas.
Out of curiosity, timitbit, what is the value of services.settings.poll_interval
in about:config
?
Assignee | ||
Comment 8•4 years ago
|
||
Comment on attachment 9188457 [details]
Bug 1677399 - avoid re-downloading and re-processing CRLite filters/stashes that are already in cert_storage r?bbeurdouche
Beta/Release Uplift Approval Request
- User impact if declined: excess cpu usage/jank on early betas
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): relatively small change, we have test coverage, and this isn't even enabled in release yet
- String changes made/needed: none
(In reply to Dana Keeler (she/her) (use needinfo) (:keeler for reviews) from comment #7)
Yes - this isn't enabled in release yet, but it will affect early betas.
Out of curiosity, timitbit, what is the value of
services.settings.poll_interval
inabout:config
?
services.settings.poll_interval = 86400
Comment 10•4 years ago
|
||
Comment on attachment 9188457 [details]
Bug 1677399 - avoid re-downloading and re-processing CRLite filters/stashes that are already in cert_storage r?bbeurdouche
Approved for 84.0b4.
Comment 11•4 years ago
|
||
bugherder uplift |
Description
•