Serialize access to sessionsPendingDeletion
Categories
(Firefox for Android :: Browser Engine, defect)
Tracking
()
People
(Reporter: boek, Assigned: boek, NeedInfo)
References
(Regression)
Details
(Keywords: crash, regression, Whiteboard: [fxdroid][group1])
Crash Data
Attachments
(3 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
We believe that this may be a regression caused by Bug 1892751 but the stack trace isn't very clear.
Updated•27 days ago
|
Assignee | ||
Comment 1•27 days ago
|
||
Updated•27 days ago
|
Comment 2•23 days ago
|
||
Does this crash only affect users with SHIP enabled? I suspect all users are potentially affected because this crash is one of our top crashes in Beta 136, where SHIP is not enabled. We should consider uplifting this fix to Beta 137 or even a 136.x dot release if we see these crashes in Release.
Assignee | ||
Comment 3•23 days ago
|
||
Assigned reviewers and posted in the broader chat channel to see if we can get a review for this patch
Comment 4•23 days ago
|
||
Tracking since the volume is higher in 136 than 135.
We should include this in next week's planned Android release for Fx136.
Comment 7•22 days ago
|
||
The patch landed in nightly and beta is affected.
:boek, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox137
towontfix
.
For more information, please visit BugBot documentation.
Comment 8•22 days ago
|
||
Adding to Comment 7, please add a release uplift request also.
It will have coverage in nightly and beta before we go to release.
Assignee | ||
Comment 9•21 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D239962
Updated•21 days ago
|
Assignee | ||
Comment 10•21 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D239962
Updated•21 days ago
|
Comment 11•21 days ago
|
||
release Uplift Approval Request
- User impact if declined: Users will experience this crash in 136
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: Delete tabs using the tabs tray
- Risk associated with taking this patch: Low
- Explanation of risk level: Adds a mutex, but code is easy to understand. May be close to medium as it has not had time to bake in Nightly or Beta
- String changes made/needed: none
- Is Android affected?: yes
Comment 12•21 days ago
|
||
beta Uplift Approval Request
- User impact if declined: Users will experience this crash in 137
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: Delete tabs using the tabs tray after browsing.
- Risk associated with taking this patch: Low
- Explanation of risk level: Adds a mutex, but code is easy to understand. May be close to medium as it has not had time to bake in Nightly or Beta
- String changes made/needed: None
- Is Android affected?: yes
Updated•21 days ago
|
Comment 13•21 days ago
|
||
uplift |
Updated•21 days ago
|
Updated•17 days ago
|
Comment 14•17 days ago
|
||
uplift |
Updated•17 days ago
|
Comment 15•16 days ago
|
||
This issue is verified as fixed on Firefox Nightly 138 (2025-03-10), Firefox 137 Beta 4 and Firefox RC 136.0.1 under Samsung S24 Ultra (Android 14) and Google Pixel 8 (Android 15). No crash was encountered when closing tabs from tabs tray.
Description
•