[Webkit-unassigned] [Bug 30510] New: Serializing a jQuery Object with jsDump can often kill the computer

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=30510

           Summary: Serializing a jQuery Object with jsDump can often kill
                    the computer
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: spamfaenger at gmx.de


There are mostly two scenarios that play out here:

a) The "slow script warning" kicks in and after the offered abort of the script
Safari uses _lots_ of megabytes more memory that seems to be only reclaimable
by restarting the browser or
b) The computer just comes to a grinding halt as it is swapping gigabytes of
memory in and out. If I am fast enough I can usually kill Safari before my
mashine doesn't respond in any way anymore - but I need to be quick for this.

I think that this should not be possible - if a webpage is using some gigabytes
of memory in a computation, Safari should protect my computer from getting
bogged down by this.

Some notes on the setup. I haven't yet reduced this down completely, but here's
how it happens.

Using: jQuery 1.3.2, jQuery-UI 1.7.2, jsDump 1.0.0

I have a page with some <dl><dt/><dd/><dd/></dl> and then do some code roughly
equivalent to this:

$('dl').draggable()
jsDump.parse($('dl').data('draggable'))

(Actually that is one of my unittests failing and then trying to stringify the
results of that data-call).

So please fix it.

Regards,
Martin

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.