Bug 4580

Summary:

WebCore+SVG asserts when running JavaScript

Product:

WebKit

Reporter:

Eric Seidel (no email) <eric>

Component:

SVG

Assignee:

Eric Seidel (no email) <eric>

Status:

RESOLVED FIXED

Severity:

Normal

Priority:

Version:

420+

Hardware:

Mac

OS:

OS X 10.4

Attachments:

Description	Flags
A simple javascript SVG which asserts	none
Adds necessary Interpreter::lock()/unlock() calls.	darin: review+

Eric Seidel (no email)

Reported 2005-08-22 01:37:18 PDT

As part of recent changes in JSC, more Interpreter::lockCount() asserts were added, thus causing WebCore +SVG to fail in more places. Attached is an example SVG which asserts.

Attachments
A simple javascript SVG which asserts (2.32 KB, image/svg+xml) 2005-08-22 01:38 PDT, Eric Seidel (no email)	no flags	Details
Adds necessary Interpreter::lock()/unlock() calls. (1.06 KB, patch) 2005-08-22 02:01 PDT, Eric Seidel (no email)	darin: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Eric Seidel (no email)

Comment 1 2005-08-22 01:38:03 PDT

Created attachment 3505 [details] A simple javascript SVG which asserts

Eric Seidel (no email)

Comment 2 2005-08-22 02:01:58 PDT

Created attachment 3507 [details] Adds necessary Interpreter::lock()/unlock() calls.

Darin Adler

Comment 3 2005-08-22 08:18:36 PDT

Comment on attachment 3507 [details] Adds necessary Interpreter::lock()/unlock() calls. Looks fine. The APPLE_CHANGES should not be necessary, because the lock/unlock functions should be empty inlines when locking is not necessary, but I guess that's not how JavaScriptCore is right now. r=me

Note You need to log in before you can comment on or make changes to this bug.