Closed Bug 289032 Opened 20 years ago Closed 20 years ago

Crash/hang with this evil testcase (overflow:scroll; position:absolute)

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: martijn.martijn, Assigned: roc)

References

Details

(Keywords: crash, regression, testcase)

Attachments

(3 files)

Unfortunately, I am not able (yet maybe) to make the testcase any simpler.

The testcase doesn't crash or hang in the 2005-04-03 7:31am Firefox trunk build.
It crashes or hangs in the 2005-04-04 7:23am Firefox trunk build.
My guess would be that it is a regression from bug 288117.
The crash should normally happen within 10s or so.
I'll attach stacktraces from my up to date debug build.
Attached file Testcase
Attached file Stacktrace1
This is the stacktrace from the assertion I get before the crash:
###!!! ASSERTION: Bogus state: '!mLastChild->GetNextSibling()
Attached file Stacktrace2
This is the stacktrace from the actual crash.
Depends on: 289123
roc, this looks like you.... 
Assignee: nobody → roc
Flags: blocking1.8b2?
Flags: blocking-aviary1.1?
In GTK2, this triggers tons of assertions about widget reparenting not being
implemented --- but we don't crash. My guess is that although widget reparenting
is implemented in Windows, it's unreliable and eventually corrupts things. The
patch in bug 288949 avoids widget reparenting; my guess is that it will fix this
bug.
Depends on: 288949
Keywords: testcase
Ok, this seems to be fixed by the fix for bug 288949. It can crash for me with
2005-04-07 build, but I can't make it crash with 2005-04-08 build.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Flags: blocking1.8b2?
Flags: blocking-aviary1.1?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: