[Webkit-unassigned] [Bug 170748] New: WebAssembly: improve GC for fast memory

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 11 13:58:17 PDT 2017


            Bug ID: 170748
           Summary: WebAssembly: improve GC for fast memory
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jfbastien at apple.com
                CC: fpizlo at apple.com, jfbastien at apple.com,
                    keith_miller at apple.com, mark.lam at apple.com,
                    msaboff at apple.com, sbarati at apple.com
        Depends on: 170628
            Blocks: 159775

As part of bug #170628 I'm tuning how we call GC for fast memories: running the GC could free some up. The code currently calls collectAllGarbage in the current VM.

We could be smarter though:

1. We pass in the *current* VM to call a GC on. Nothing tells us that the current VM is holding onto a fast memory, it could be any VM. Should we instead iterate all of them, and GC the ones which are using wasm?
2. collectSync(Full) and custom eager destruction of wasm memories could be better. That would mean that we have a separate space where we track all fast memories, so we can sweep the dead ones without sweeping everything else.

Referenced Bugs:

[Bug 159775] WebAssembly: support the newer spec
[Bug 170628] WebAssembly: manage memory better
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170411/c72a836b/attachment.html>

More information about the webkit-unassigned mailing list