Closed
Bug 1254276
Opened 9 years ago
Closed 5 years ago
Too-much-recursion crash with filter, sticky pos
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox47 | --- | affected |
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: crash, hang, testcase)
Attachments
(3 files)
Stack and testcase is somewhat similar to bug 866767, but this testcase doesn't use "filter: url()", which Mats identified as important in bug 866767 comment 3.
ASan Opt
Reports "stack-overflow". Fails to produce a stack trace, showing only a top frame unlucky enough to the stack barrier.
Release opt
Reports what looks like a stack overflow. Similarly fails to produce a stack trace. bp-884771c5-236a-4242-ba82-784e02160307
Debug
Hangs due to hitting too many non-fatal assertions. The assertion failures have a repeating stack portion, so I assume this is the same repeating portion that eventually leads to a crash in non-debug builds.
The repeating portion of the stack is:
> #122: PresShell::ProcessReflowCommands(bool) [layout/base/nsPresShell.cpp:9125]
> #123: PresShell::FlushPendingNotifications(mozilla::ChangesToFlush) [layout/base/nsPresShell.cpp:4069]
> #124: PresShell::DidDoReflow(bool) [mfbt/RefPtr.h:296]
> #125: PresShell::ProcessReflowCommands(bool) [layout/base/nsPresShell.cpp:9125]
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
This one doesn't use filters at all.
Comment 3•5 years ago
|
||
Following the reporter's steps I am able to confirm that the issues doesn't happen anymore on Windows 10 and MacOs 10.15 on any of the current versions of Firefox Nightly 87.0a1 (2021-02-16), beta 86.0 and release 85.0.2. The example test cases don't crash/hang Firefox anymore.
Closing this issue as Resolved > Worksforme.
Feel free to re-open or file a new bug if this issue reoccurs again.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•