[Webkit-unassigned] [Bug 172710] REGRESSION(r216759-216775): Dromaeo jslib-modify-jquery crashes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 30 08:05:21 PDT 2017


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

Andreas Kling <akling at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ggaren at apple.com,
                   |                            |msaboff at apple.com

--- Comment #6 from Andreas Kling <akling at apple.com> ---
(In reply to Yusuke Suzuki from comment #5)
> (In reply to Andreas Kling from comment #4)
> > Or hmm, looking at the test, IIUC it measures jQuery performance by creating
> > this fragment:
> > 
> > <strong>some text</strong>
> > 
> > ...and inserting as many of them as possible into the document in a certain
> > time. This kind of test is indeed going to hit our memory limits now that
> > they are down to 4GB, since computers (and WebKit!) are too damn fast. :|
> 
> Yeah, I've just checked it with resource overlay and seen that bmalloc
> memory becomes huge while GC heap is still ~300MB.

Most of that bmalloc memory is very likely a bajillion DOM nodes (<strong> elements and Text nodes), I bet. They probably all have a JS DOM wrapper each, but even if we could GC those we'd only recover the wrapper memory, since the nodes are still physically inserted in the DOM.

I'm unsure what the right solution would be here. I mean, if we raise the limit, there will still come a day when we get so fast at creating and inserting DOM nodes, that we exceed the new limit :)

+CC Geoff and Michael for thoughts

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170530/14249b27/attachment.html>


More information about the webkit-unassigned mailing list