Bug 1624878 Comment 23 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

If the crash rate increased for this specific collection `security-state/intermediates`, then it is related to the work we did in Bug 1889617.

Basically, instead of initiating 1700+ requests on tiny .pem files, we now download a single zip file and extract its content in the IndexedDB attachments storage (ie. 1700+ calls to ([`saveAttachments()`](https://searchfox.org/mozilla-central/rev/02a4a649ed75ebaf3fbdf301c3d3137baf6842a1/services/settings/Database.sys.mjs#235-255) from a [`client.attachments.cacheAll()`](https://searchfox.org/mozilla-central/rev/02a4a649ed75ebaf3fbdf301c3d3137baf6842a1/services/settings/Attachments.sys.mjs#221-253) method).

In theory, our IndexedDB code is instrumented with shutdown blockers (:Gijs helped us do this years ago :)), but there could be bugs where the code escapes the blocker (ie. Bug 1890278)?

We are not advanced platform developers, with fast hardware, etc. Hence we would clearly need help to dive into this issue and fix it :/
If the crash rate increased for this specific collection `security-state/intermediates`, then it is related to the work we did in Bug 1889617.

Basically, instead of initiating 1700+ requests on tiny .pem files, we now download a single zip file and extract its content in the IndexedDB attachments storage (ie. 1700+ calls to ([`saveAttachments()`](https://searchfox.org/mozilla-central/rev/02a4a649ed75ebaf3fbdf301c3d3137baf6842a1/services/settings/Database.sys.mjs#235-255) from a [`client.attachments.cacheAll()`](https://searchfox.org/mozilla-central/rev/02a4a649ed75ebaf3fbdf301c3d3137baf6842a1/services/settings/Attachments.sys.mjs#221-253) method).

In theory, our IndexedDB code is instrumented with shutdown blockers (:Gijs helped us do this years ago :)), but there could be bugs where the code escapes the blocker (ie. Bug 1890278)?

We are not advanced platform developers, and have fast hardware, etc. Hence we would clearly need help to dive into this issue and fix it :/

Back to Bug 1624878 Comment 23