Open RubenKelevra opened 3 months ago
Looks like it's crashing trying to draw an SVG Circle element. Is there a way to isolate the specific SVG into a smaller test case?
Looks like the only GCPtr
dereferenced in SVGCircleElement::get_path
is coming from layout_node()
.
Not sure how that can be null, since get_path
is called via <layout_node>.dom_node().get_path(...)
.
Looks like it's crashing trying to draw an SVG Circle element. Is there a way to isolate the specific SVG into a smaller test case?
I've tried loading the svgs on the page one by one directly and it doesn't seem to be the issue.
I think something else is going on, unrelated to the SVG parsing itself.
I can confirm the bug for 69da6a0ce40, after the fix for telekom.de (#661) in #704.
I was able to reduce the error to this piece of html:
<!doctype html>
<svg>
<rect clip-path="url(#clip-path)"></rect>
<defs>
<clipPath id="clip-path">
<circle cx="30" cy="30" r="30"></circle>
</clipPath>
</defs>
</svg>
Some observations:
<rect>
and <circle>
, when I remove either or those the crash does not happen anymore. url(#a)
-> id="b"
<defs>
above the <rect>
it does not crash.I can confirm that 34261e54901 will still crash when visiting https://t-online.de
I'm using 09f76098b06804efb1f82f2244338ad4a97c9cfb of Ladybird under Linux x86_64 and found that it consistantly crash if trying to load one of the most notriously overloaded German websites
https://t-online.de
.Sometimes it even crashes the whole browser. So I thought I add the crashlog here: