Large scale in crashtest 1608851.html can cause OOM on mulitple platforms, including Android, Windows, and macOS
Categories
(Core :: Web Painting, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: TYLin, Assigned: dholbert)
References
Details
Attachments
(1 file)
Filed per mats' suggestion in bug 1584890 Comment 19.
After fixing bug 1584890, layout/generic/crashtests/1608851.html
which has a large scale in the style sheet can cause OOM crash on Android.
The test doesn't crash on desktop, but it does yield a warning like [GFX3-]: Surface size too large (exceeds extent limit)!
I'm planning to reland bug 158489 with the test disabled on Android.
Comment 1•4 years ago
|
||
(In reply to Ting-Yu Lin [:TYLin] (UTC-7) from comment #0)
After fixing bug 1584890,
layout/generic/crashtests/1608851.html
which has a large scale in the style sheet can cause OOM crash on Android.
the test file will be renamed. I am putting a perma link to the old one;
https://searchfox.org/mozilla-central/rev/df4c90d4b8c92c99f76334acfe4813c573c12661/layout/generic/crashtests/1608851.html#8
Reporter | ||
Comment 2•4 years ago
|
||
Thanks hiro! The old one is going to be renamed to 1608851-1.html
in https://phabricator.services.mozilla.com/D76411
Comment 3•4 years ago
|
||
The severity field is not set for this bug.
:mattwoodrow, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Assignee | ||
Comment 4•2 years ago
•
|
||
It looks like we can re-enable this crashtest now. At least: I did a try push with the test reenabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=4d142a6b8a322ac1b89112e0c49254d6b0ee9564
...and I retriggered Android crashtest runs (8 iterations on opt, 8 iterations on debug), and I never hit any issues.
Given that the original Android issue cropped up on the very first TreeHerder run (based on cset in the "push" link in bug 1584890 comment 17), and now we can reenable and retrigger 8x without hitting a single issue, it looks like the underlying issue has gone away or morphed such that we're OK to have this enabled now.
(Possibly this was addressed by WebRender being enabled, given that we had some warning text that alluded to large graphics layers/surfaces being allocated)
Assignee | ||
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
bugherder |
Description
•