nsCertVerificationThread is used very rarely by most users since it is only used in the cert management UI and for S/MIME validation. Since it is used so rarely in Firefox and Thunderbird, we should not start the thread at startup but instead do so only when it is accessed. And, we should shut down the thread when the certificate validation is complete (perhaps, waiting a bit in case there are multiple validations that happen one-after-another, as might be common with Thunderbird S/MIME validation). I do not know the memory overhead of a single stack or how much time this adds to startup, so I cannot estimate the impact.
MemShrink:P3 for now, if we get measurements showing the effect we can reprioritize. (Also, would measuring this in about:memory be worthwhile?)
Whiteboard: [Memshrink?] → [Memshrink:P3]
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.