[Webkit-unassigned] [Bug 95376] Dromaeo jquery DOM modification tests run out of memory and crash in current WebKit

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 29 16:06:10 PDT 2012


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


Ryosuke Niwa (vacation: 8/26-9/10) <rniwa at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |haraken at chromium.org,
                   |                            |morrita at google.com




--- Comment #4 from Ryosuke Niwa (vacation: 8/26-9/10) <rniwa at webkit.org>  2012-08-29 16:06:14 PST ---
Thanks for analysis, Boris!

(In reply to comment #2)
> So it's possible that it's not a regression in WebKit as much as a problem with something jquery 1.6.4 is doing.
> 
> I also tried jquery 1.8.0 (current stable tip) and the same OOM happens.

The last time we analyzed, the problem with the test itself. It doesn't garbage remove the container node it adds, so the test ends up consuming ~4GB of RAM as we run more "runs". I bet the problem is the newer version of jquery is that it's faster, and WebKit is able to run more "runs", consuming more memory.

(In reply to comment #3)
> One other thing confusing me:  I think this test is operating on disconnected subtrees.  Why is there layout involved at all?

It's connected to the document :( But how are you determining whether there is a layout or not?

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



More information about the webkit-unassigned mailing list