RESOLVED FIXED 54546
Crash when rendering a deeply-nested SVG 
https://bugs.webkit.org/show_bug.cgi?id=54546
Summary Crash when rendering a deeply-nested SVG
Johannes Rössel
Reported 2011-02-16 04:47:17 PST
Created attachment 82613 [details] Sixth-generation Sierpinski carpet, crashes Chrome and Safari on Windows immediately The image in question is a Sierpinski carpet re-using the previous generation with <use> for each generation. Chrome and Safari each die almost immediately on Windows. Chrome on Linux needs http://hypftier.de/temp/Sierpinski%20carpet%207.svg to crash instead, the sixth generation does not appear to crash instantly.
Attachments
Sixth-generation Sierpinski carpet, crashes Chrome and Safari on Windows immediately (74 bytes, text/plain)
2011-02-16 04:47 PST, Johannes Rössel 		no flags
Details
Seventh-generation Sierpinsky carpet. Crashes Chrome on Linux instantly. (4.13 KB, image/svg+xml)
2011-02-16 04:49 PST, Johannes Rössel 		no flags
Details
Sixth-generation Sierpinski carpet, crashes Chrome and Safari on Windows immediately (3.47 KB, image/svg+xml)
2011-02-16 04:49 PST, Johannes Rössel 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Johannes Rössel
Comment 1 2011-02-16 04:49:03 PST
Created attachment 82614 [details] Seventh-generation Sierpinsky carpet. Crashes Chrome on Linux instantly.
Johannes Rössel
Comment 2 2011-02-16 04:49:38 PST
Created attachment 82615 [details] Sixth-generation Sierpinski carpet, crashes Chrome and Safari on Windows immediately
Nikolas Zimmermann
Comment 3 2011-03-30 00:48:44 PDT
Thanks Jonathan, your bug is fixed in the latest nightly. We can now render generation 6 w/o a problem. I'm not sure if the speed is acceptable, I've only tried a local debug build, maybe you can report back. Just testing generation 7.
Dirk Schulze
Comment 4 2011-05-22 05:54:40 PDT
The bug is fixed, but I'd like to land the test as a performance test.
Dirk Schulze
Comment 5 2011-05-22 05:58:49 PDT
Oh, we already have it in trunk. Closing bug now.
Note You need to log in before you can comment on or make changes to this bug.