Infinite loop in `position-anchor` layout
Categories
(Core :: Layout: Positioned, defect, P2)
Tracking
()
People
(Reporter: chrisxuche, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files, 3 external files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:155.0) Gecko/20100101 Firefox/155.0
Steps to reproduce:
Reproduce:
I captured the stack trace and coredump after I encountered this bug.
I handed the backtrace and core file to my AI agent, they gave me the minimal reproducible example HTML file. I checked and it can reproduce.
- I'm running latest ArchLinux + Wayland + KDE. See my setup in attached
about:supportfile - Create a new profile.
- Go to
about:configand setwidget.gtk.overlay-scrollbars.enabledtofalse. - Open the attached HTML file.
- Infinite loop in content process, eats one full CPU core.
- Can't gracefully shutdown browser because it's in infinite loop.
GDB backtrace is also attached.
BTW:
Seems it's cause by a skipped result write back of the if (currentFallbackIndex) block.
(I need to figure out how to put multiple attachments on Enter Bug page...)
Updated•1 month ago
|
Updated•1 month ago
|
Comment 3•1 month ago
|
||
Comment 4•1 month ago
|
||
:emilio, since you are the author of the regressor, bug 1897279, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 5•1 month ago
|
||
| Assignee | ||
Comment 6•1 month ago
|
||
Thanks for the reduced test-case! Curious, did you spot it on the wild? That would help in terms of considering uplifting the fix to beta / release.
Yes. I found it when I was using https://chatgpt.com, the page froze when I tried to scroll
Comment 8•1 month ago
|
||
Set release status flags based on info from the regressing bug 1897279
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62567 for changes under testing/web-platform/tests
Comment 12•1 month ago
|
||
| bugherder | ||
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Comment 13•1 month ago
|
||
If a fallback used to fit, but after fallback none of the positions fit,
we end up in the base position, but we didn't clear the last index
properly, so the fallback reflow kept triggering.
Move the clear to after the loop, and add a test that repros with or
without overlay scrollbars. Add also the test as a crashtest.
Pull request: https://github.com/mozilla-firefox/firefox/pull/362
Updated•1 month ago
|
Comment 14•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Causes content process hang in realistic scenarios (chatgpt.com seems to be affected for example).
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: Relatively straight-forward fix.
- String changes made/needed?: none
- Is Android affected?: yes
Upstream PR merged by moz-wptsync-bot
Comment 16•1 month ago
|
||
Comment on attachment 9640298 [details]
Bug 2070171 - Clear last fallback properly when don't fit after fitting.
It's too late for Fx156 beta, switching the request to release for the planned dot release
Comment 18•1 month ago
|
||
firefox-esr153 Uplift Approval Request
- User impact if declined/Reason for urgency: See above
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: see above
- Risk associated with taking this patch: low
- Explanation of risk level: see above
- String changes made/needed?: none
- Is Android affected?: yes
| Assignee | ||
Comment 19•1 month ago
|
||
If a fallback used to fit, but after fallback none of the positions fit,
we end up in the base position, but we didn't clear the last index
properly, so the fallback reflow kept triggering.
Move the clear to after the loop, and add a test that repros with or
without overlay scrollbars. Add also the test as a crashtest.
Pull request: https://github.com/mozilla-firefox/firefox/pull/362
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 20•1 month ago
|
||
I was able to reproduce the issue on Ubuntu 24.04 using FF build 155.0.1.
Verified as fixed on Ubuntu 24.04 using FF build 158.0a1 and 157.0b1.
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 21•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 22•1 month ago
|
||
| uplift | ||
Comment 23•1 month ago
|
||
Issue is fixed as I could not replicate on Ubuntu 24.04 using Firefox build 156.0.1(20260921121718).
Comment 24•1 month ago
|
||
Verified as fixed on Ubuntu 24.04 using Firefox build 153.4.0esr.
Description
•