Bug 5792 - Crasher on rendering-shapes from SVG 1.0 testsuite
Summary: Crasher on rendering-shapes from SVG 1.0 testsuite
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P1 Normal
Assignee: Nobody
URL: http://www.w3.org/Graphics/SVG/Test/2...
Keywords:
Depends on:
Blocks: 6390
  Show dependency tree / graph
 
Reported: 2005-11-21 07:00 PST by Rob Buis
Modified: 2019-02-06 09:02 PST (History)
1 user (show)

See Also:

Attachments
test case (235 bytes, application/xhtml+xml)
2006-01-05 15:32 PST, Alexey Proskuryakov 		no flags Details
proposed fix (4.27 KB, patch)
2006-01-05 16:44 PST, Alexey Proskuryakov 		eric: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Buis 2005-11-21 07:00:34 PST 
Using the latest Webkit cvs checkout (with svg enabled) and using
run-safari --svg the mentioned svg crashes safari on my system.
Comment 1 Eric Seidel (no email) 2005-12-05 03:16:54 PST 
I too have seen a crash when browsing the 1.0 test suite:
http://www.w3.org/Graphics/SVG/Test/20011026/rendering-shape-BE-03-ps.html

I'm not yet sure why.
Comment 2 Eric Seidel (no email) 2005-12-05 03:26:09 PST 
Yes, this is what I expected.  This is another example of the misterious libxml crash:

#0	??
#1	0x92c0b054 in xmlParseCharData
#2	0x92c26fb0 in xmlParseContent
#3	0x92c2a4f4 in xmlParseBalancedChunkMemory
#4	0x92c2313c in xmlParseReference
#5	0x92c28704 in xmlParseDocument
#6	0x92c0cc0c in xmlParseChunk
#7	0x0184d118 in khtml::parseQString at xml_tokenizer.cpp:188
#8	0x0184e67c in khtml::XMLTokenizer::finish at xml_tokenizer.cpp:646
#9	0x018123ec in DOM::DocumentImpl::finishParsing at dom_docimpl.cpp:1568
#10	0x016c1b88 in KHTMLPart::endIfNotLoading at khtml_part.cpp:1115
#11	0x016c1bdc in KHTMLPart::end at khtml_part.cpp:1103
#12	0x016a5dd8 in -[WebCoreBridge end] at WebCoreBridge.mm:521

It looks to me like a bug in libxml, but I'm not sure.
Comment 3 Alexey Proskuryakov 2006-01-05 15:32:22 PST 
Created attachment 5505 [details]
test case
Comment 4 Alexey Proskuryakov 2006-01-05 15:35:00 PST 
Apparently, something doesn't like entity declarations where content starts with a whitespace.
Comment 5 Eric Seidel (no email) 2006-01-05 16:43:42 PST 
ap noted in IRC this might be: http://bugzilla.gnome.org/show_bug.cgi?id=172255  he has a workaround 
patch.
Comment 6 Alexey Proskuryakov 2006-01-05 16:44:24 PST 
Created attachment 5507 [details]
proposed fix

Work around <http://bugzilla.gnome.org/show_bug.cgi?id=172255>.
Comment 7 Eric Seidel (no email) 2006-01-05 16:50:18 PST 
Comment on attachment 5507 [details]
proposed fix

Beautiful.  r=me
Comment 8 Lucas Forschler 2019-02-06 09:02:45 PST 
Mass moving XML DOM bugs to the "DOM" Component.