Land crashtest for bug 1517025
Categories
(Core :: Networking, enhancement, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
See https://phabricator.services.mozilla.com//D16817
The crashtest triggers some assertions on OSX
[Child 1950, Main Thread] ###!!! ASSERTION: bad inline size: 'reflowOutput.ISize(lineWM) >= 0', file /builds/worker/workspace/build/src/layout/generic/nsLineLayout.cpp, line 962
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=223031965&repo=autoland&lineNumber=24354
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
It would seem there are still assertions here.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=36707cd9601f8488063caf7df1e93a9c29af0908&selectedTaskRun=RyHHgzjdQGOxfljxGXuyFg.0
The unit tests I landed for bug 1517025 are enough to prevent regressions of the security bug.
We have this problem in a bunch of other tests (see bug 1305241).
Maybe we should just remove the assertions at some point? Or are they actually useful?
Updated•4 years ago
|
Comment 3•4 years ago
|
||
So those assertions are useful in the sense that they should only fire with degenerate test-case. I'm very confused about how your test-case could trigger it, they likely come from another crashtest? It has nsTableWrapperFrame
in the stack and there's no table in your test-case at all... However that shouldn't stop you from landing it, just add an asserts(0-1)
annotation to the crashtest list and file a bug so that we can investigate?
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
Thanks for the suggestion. Really useful.
Comment 6•4 years ago
|
||
bugherder |
Description
•