Closed Bug 1683863 Opened 3 years ago Closed 2 years ago

Investigate mitigated-by-backout reproducible crash on startup [@ mozilla::dom::quota::QuotaManager::InitializeOrigin ]

Categories

(Core :: Storage: Quota Manager, defect, P3)

x86_64
macOS
defect

Tracking

()

RESOLVED WORKSFORME
86 Branch
Tracking Status
firefox86 --- wontfix

People

(Reporter: Tobbi, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Crash Data

Attachments

(1 file)

Since updating to the latest nightly, my Firefox Nightly keeps crashing. Here is one of the crash reports:
https://crash-stats.mozilla.org/report/index/bc276359-909f-433c-810b-c45630201222#tab-details

about:support content is here: https://pastebin.com/j27BhFXZ

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: General → Storage: Quota Manager
Product: Firefox → Core
Flags: needinfo?(sgiesecke)
Regressed by: 1679540
Has Regression Range: --- → yes
Crash Signature: [@ mozilla::dom::quota::QuotaManager::InitializeOrigin ]
Flags: needinfo?(sgiesecke)

Thanks for reporting that! I see there are such crashes from three installations so far.

Bug 1679540 promoted the overflow check, which is now at https://hg.mozilla.org/mozilla-central/annotate/54a95a4088a237cd14acc087cb433cb43216fbd1/dom/quota/ActorsParent.cpp#l5386, from a debug assertion to a diagnostic assertion, which is active in Nightly. Probably there was an overflow happening in the old code, but it just resulted in a wrong usage value immediately being passed to InitQuotaForOrigin. Maybe that resulted in a storage initialization error later on, but not a crash?

I'll request backout and provide a safer patch after the holidays.

:Tobbi, can you save your profile, and would you be willing to share it with us, so we can understand the root cause of this overflow?

Did you encounter any storage-related issues with that profile before the Nightly update?

Flags: needinfo?(tobbi.bugs)

I have several privacy-related concerns about sharing my profile, since this is my main Firefox profile and it contains a lot of sensitive data. Is there any way I can share the contents with you privately? The size of the compressed file is around 400 MB

I did not knowingly encounter any storage-related issues with that profile before.

Flags: needinfo?(tobbi.bugs)

We understand your privacy concerns. We will check if there are other ways to better understand the root cause of the issue, but we will only be able to get back to this after the holidays.

The current Nightly should work again, as the patch that has likely caused the startup crash has been backed out.

Since the code causing the problem was backed out I'm repurposing this bug to track the investigation of the problem, but it could also make sense to close this in favor of tracking on the regressing bug.

Severity: -- → S3
Priority: -- → P3
Summary: Reproducible crash on startup [@ mozilla::dom::quota::QuotaManager::InitializeOrigin ] → Investigate mitigated-by-backout reproducible crash on startup [@ mozilla::dom::quota::QuotaManager::InitializeOrigin ]

A modified patch now landed and this should no longer lead to a crash. However, I think you might have a storage initialization failure now. Could you check that and share the results of visiting https://firefox-storage-test.glitch.me/?

Flags: needinfo?(tobbi.bugs)
Assignee: nobody → sgiesecke
Status: NEW → ASSIGNED
Pushed by sgiesecke@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8a6a31fa9985
Log sources of negative usage values to browser console. r=dom-workers-and-storage-reviewers,janv
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
Status: RESOLVED → REOPENED
Keywords: leave-open
Resolution: FIXED → ---

:tobbi, sorry I didn't wait for a response from you. I had another idea to mitigate the issue. I think that any storage initialization failure due to the underlying issue should now be resolved in the latest Nightly, but the corrupted storage directories probably still remain, and might render specific origins still unusable. Can you check your browser console for any QuotaManager warning?

I just restored my profile from the backup I made in December and updated to the latest nightly (I restored my Nightly due to other issues). There are no QuotaManager warnings in the browser console with the latest nightly and the contents of the backup profile.

Flags: needinfo?(tobbi.bugs)
Flags: needinfo?(sgiesecke)

I won't get to this, unassigning and clearing NI.

Assignee: sgiesecke → nobody
Flags: needinfo?(sgiesecke)

The leave-open keyword is there and there is no activity for 6 months.
:jstutte, maybe it's time to close this bug?

Flags: needinfo?(jstutte)

(In reply to Tobias (:Tobbi) Markus from comment #11)

I just restored my profile from the backup I made in December and updated to the latest nightly (I restored my Nightly due to other issues). There are no QuotaManager warnings in the browser console with the latest nightly and the contents of the backup profile.

Hi :tobbi, is there still something not working for you here? I assume you did not experience that crash anymore?

Flags: needinfo?(jstutte) → needinfo?(tobbi.bugs)

It doesn't look like this is an issue anymore. I haven't had any crash with that signature since the backout.

Flags: needinfo?(tobbi.bugs)

The leave-open keyword is there and there is no activity for 6 months.
:jstutte, maybe it's time to close this bug?
For more information, please visit auto_nag documentation.

Flags: needinfo?(jstutte)

The very few remaining crashes seem unrelated to this investigation (the signature's function is quite big).

Status: REOPENED → RESOLVED
Closed: 3 years ago2 years ago
Flags: needinfo?(jstutte)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: