Closed
Bug 1429215
Opened 7 years ago
Closed 7 years ago
Make assertion condition more sensitive / less crashy in GetFloatFromPlaceholder
Categories
(Core :: Layout, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla59
Tracking | Status | |
---|---|---|
firefox59 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
References
Details
Attachments
(1 file)
As noted in bug 1429172 comment 1: That bug's testcase currently crashes debug builds **while we're evaluating the assertion condition**. We crash because the assertion dereferences a pointer that we haven't bothered to null-check (because we have good reason to believe it should be non-null, though in this case it does happen to be null, hence we crash).
We should just broaden the assertion to *also* assert that the pointer is non-null, so that we fail the assertion rather than crashing inside of its condition.
Comment hidden (mozreview-request) |
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8941203 [details]
Bug 1429215: Null-check pointer before using it in assertion in GetFloatFromPlaceholder() (to avoid crashing during assertion).
https://reviewboard.mozilla.org/r/211472/#review217308
Attachment #8941203 -
Flags: review?(mats) → review+
Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bef5e30e6243
Null-check pointer before using it in assertion in GetFloatFromPlaceholder() (to avoid crashing during assertion). r=mats
Comment 4•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox59:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in
before you can comment on or make changes to this bug.
Description
•