Memory-pressure regression misses remaining GC clock and timer traps

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, wasm
Domain
testing

Research direction

Start with the memory-pressure test added in #60 and the regression test in #78, then reproduce the failures on Go 1.26.3 or 1.27.1 with the Wasmtime 48.0.2 adapter. Done means the strengthened test reliably covers wall-time and timer polling during cabi_realloc without either path trapping; review the linked adapter fix for the work already underway.

Written by the indexing model from the issue text.

Description

The GC failure reported in #56 still occurs when Go reads wall time or polls timers during cabi_realloc. Both can trap with cannot leave component instance.

The memory-pressure test added in #60 does not reliably trigger these paths. Strengthening it exposes both failures on Go 1.26.3 and 1.27.1 with the Wasmtime 48.0.2 adapter.

Regression test: #78. Adapter fix: https://github.com/bytecodealliance/wasmtime/pull/14319, extending the clock pause from https://github.com/bytecodealliance/wasmtime/pull/13563.

Dominant language
Rust
Stars
18
Forks
8
Avg merge
6h 57m
Merged PRs (30d)
5

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.

More from bytecodealliance/componentize-go

All issues in bytecodealliance/componentize-go

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.