Add some diagnostic asserts to `PresShell::MarkFramesInSubtreeApproximatelyVisible`
Categories
(Core :: Layout, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
The crashes in bug 1708808 seem to be hitting garbage data (mix of null, 0xfff..., and near-null addresses).
Some appear to be "true" null derefs, which we can at least assert about, which we can perhaps use to gather a bit more information if the assertions fail.
Let's add a couple diagnostic asserts to MarkFramesInSubtreeApproximatelyVisible
to validate that child-frame pointers in that function are non-null, to make assumptions a bit more explicit and perhaps get a bit closer to understanding what's going on.
Assignee | ||
Comment 1•3 years ago
|
||
This API only should never receive a null frame pointer (and child frames
should never be null); but we occasionally get crash reports in this function
where a null frame pointer seems to be involved. This patch's diagnostic
asserts will help us catch these crashes slightly earlier and more directly,
and might help us reason about what's going on a bit better.
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
(This assert should be trivially satisfied, but nonetheless we get crash
reports that suggest we have null pointers here, so let's see...)
Comment 5•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/5816896351a6
https://hg.mozilla.org/mozilla-central/rev/ea0aad9868d4
Comment 6•3 years ago
|
||
First crash in a build with these asserts
https://crash-stats.mozilla.org/report/index/4ff8b3ed-b415-41bd-9685-f06460221002
EXCEPTION_ACCESS_VIOLATION_EXEC at 0x65746e49, so not one of the near null crashes.
Description
•