WebAssembly / WebAssembly/shared-everything-threads

Design doc for collecting shared-to-unshared edges

Open
#79 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
97
Forks
6
PR merge metrics
No merged PRs in 30d

Description

As promised, here is a link to the design doc the V8 GC team wrote on how we would be able to support collecting cycles involving shared-to-unshared cycles: https://docs.google.com/document/d/1GoIWdfsKuKb0PS3gSF8b1U0RoHs5ALPzXAMx-QPHHNg/edit#heading=h.g227de93gbi

The current plan is to not prototype this right away, and instead initially support collecting cycles with shared-to-unshared edges only when those edges are to unshared objects on the main thread. This subset of the full capability does not require any heroics in our GC because the main thread "owns" the shared heap and is already responsible for doing GC on it along with its own unshared heap.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked V8 GC design document, then compare its full shared-to-unshared cycle-collection plan with the issue's stated initial subset for main-thread-owned unshared objects. The issue does not name files, tests, or a concrete implementation boundary; completion criteria would need to be agreed before work starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.