wpt reftest svg/text/reftests/text-context-fill.svg fatally asserts on new android 14 emulator image- 2 (" MOZ_ASSERT(!OuterSVGIsCallingReflowSVG(aFrame)) (Do not call under ISVGDisplayableFrame::ReflowSVG!) [@ mozilla::SVGUtils::ScheduleReflowSVG]")
Categories
(Core :: SVG, defect)
Tracking
()
People
(Reporter: jmaher, Assigned: longsonr)
References
(Blocks 1 open bug)
Details
(Keywords: assertion)
Attachments
(1 file)
we have 2 failures:
- css/css-sizing/aspect-ratio/replaced-element-003.html (some letters have pixels, but hard to see with the naked eye): reftest-compare
- /svg/text/reftests/text-context-fill.svg - crash on debug, specifically at this asset:
MOZ_ASSERT(!OuterSVGIsCallingReflowSVG(aFrame)) (Do not call under ISVGDisplayableFrame::ReflowSVG!) [@ mozilla::SVGUtils::ScheduleReflowSVG]
Updated•9 months ago
|
Comment 1•9 months ago
|
||
Hi Robert, it seems we hit an assertion on Android. The test file was added by you before. Could you please take a look at this crash? Thanks.
Comment 2•9 months ago
|
||
aspect-ratio/replaced-element-003.html has been mentioned in Bug 1982907, so remove the dependency and perhaps we should focus on SVG part in this bug.
Updated•9 months ago
|
Comment 3•9 months ago
•
|
||
(In reply to Joel Maher ( :jmaher ) (UTC -8) from comment #0)
- css/css-sizing/aspect-ratio/replaced-element-003.html (some letters have pixels, but hard to see with the naked eye): reftest-compare
(In reply to Boris Chiou [:boris] from comment #2)
aspect-ratio/replaced-element-003.html has been mentioned in Bug 1982907, so remove the dependency and perhaps we should focus on SVG part in this bug.
I think comment 0 just had a copypaste typo: jmaher really meant to paste svg/text/reftests/text-bidi-controls-anchors-2.svg for (1) there (he mentioned letters having fuzzy pixels, and that's the one with fuzzy letters shown in comment 0's reftest-analyzer link).
But nonetheless, it's still quite different from the text-context-fill.svg fatal-assert, so I spun off bug 1982937 to cover the fuzzy failure and we can leave this bug covering the fatal assert.
Comment 4•9 months ago
|
||
Looks like bug 1797417 and bug 1825459 are both about this same assertion-failure.
For now, simplest way forward would be to just skip this test on Android 14.
| Assignee | ||
Comment 5•9 months ago
|
||
Updated•9 months ago
|
| Assignee | ||
Comment 6•9 months ago
|
||
| Reporter | ||
Comment 7•9 months ago
|
||
oh, thanks for this, I am pushing to try with android14...
https://treeherder.mozilla.org/jobs?repo=try&revision=e22e41c0ba2d6deda74b6894a2e35ed9f9e5fa9f
| Reporter | ||
Comment 8•9 months ago
|
||
this seems to be fixed :)
Updated•9 months ago
|
| Assignee | ||
Comment 9•9 months ago
|
||
My inclination is to wait till the code freeze is over before landing this. Do you need it landed sooner Joel?
Comment 11•9 months ago
|
||
Comment 12•9 months ago
|
||
| bugherder | ||
Updated•9 months ago
|
Updated•8 months ago
|
Description
•