[Webkit-unassigned] [Bug 185967] New: Rope string sweeping should avoid touching unresolved ropes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 24 16:45:27 PDT 2018


            Bug ID: 185967
           Summary: Rope string sweeping should avoid touching unresolved
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: fpizlo at apple.com

Especially when ropes are being used in anger, a lot of JSRopeString objects are never resolved.  Thus they don't need destruction.  Since destruction is expensive, that would be useful to know.

Ropes are usually unresolved because people do something like this:

var result = "";
for (things)
    result += stuff
use result

In that case, we will create a JSRopeString for each iteration of the loop, but we will only resolve the last one.  This comes up over and over again.  For example, this:

"foo" + bar + "baz" + fuzz + "buzz" + thingy + "stuff"

will create three JSRopeStrings, but only the last one will get resolved.

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/20180524/ba9eb537/attachment.html>

More information about the webkit-unassigned mailing list