RESOLVED FIXED 25092
Crash in SVGUseElement::associateInstancesWithShadowTreeElements 
https://bugs.webkit.org/show_bug.cgi?id=25092
Summary Crash in SVGUseElement::associateInstancesWithShadowTreeElements
Eric Seidel (no email)
Reported 2009-04-08 06:40:46 PDT
Crash in SVGUseElement::associateInstancesWithShadowTreeElements Discovered this while trying to make a test case for bug 23586. See attached test case. The crash is under: 0 com.apple.WebCore 0x034e62e1 WebCore::Node::nextSibling() const + 9 1 com.apple.WebCore 0x03cecd91 WebCore::SVGUseElement::associateInstancesWithShadowTreeElements(WebCore::Node*, WebCore::SVGElementInstance*) + 891 (SVGUseElement.cpp:825) 2 com.apple.WebCore 0x03cf0480 WebCore::SVGUseElement::buildPendingResource() + 1500 (SVGUseElement.cpp:398) 3 com.apple.WebCore 0x03cec5d9 WebCore::SVGUseElement::insertedIntoDocument() + 37 (SVGUseElement.cpp:115)
Attachments
stack trace of crash (33.30 KB, text/plain)
2009-04-08 06:41 PDT, Eric Seidel (no email) 		no flags
Details
stack trace of crash (34.65 KB, text/plain)
2009-04-08 06:42 PDT, Eric Seidel (no email) 		no flags
Details
test case (crashes Safari) (926 bytes, image/svg+xml)
2009-04-08 06:44 PDT, Eric Seidel (no email) 		no flags
Details
Fix ASSERT seen in shadow tree testing (3.05 KB, patch)
2009-06-04 19:28 PDT, Eric Seidel (no email) 		darin: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2009-04-08 06:41:17 PDT
Created attachment 29332 [details] stack trace of crash
Eric Seidel (no email)
Comment 2 2009-04-08 06:42:26 PDT
Created attachment 29333 [details] stack trace of crash
Eric Seidel (no email)
Comment 3 2009-04-08 06:44:01 PDT
Created attachment 29334 [details] test case (crashes Safari)
Eric Seidel (no email)
Comment 4 2009-06-04 19:28:59 PDT
Created attachment 30980 [details] Fix ASSERT seen in shadow tree testing 5 files changed, 49 insertions(+), 1 deletions(-)
Brent Fulgham
Comment 5 2009-06-09 12:35:01 PDT
Landed in @r44540.
Note You need to log in before you can comment on or make changes to this bug.