test: intermittent unit (linux) failure in abort-leak webfetch memory test

[gqcdm]

Description

unit (linux) intermittently fails in GitHub Actions on packages/opencode/test/memory/abort-leak.test.ts with:

memory: abort controller leak > webfetch does not leak memory over many invocations

This does not currently look like a deterministic regression from the reporting branch itself. The same PR later passed on re-run without touching the webfetch / abort / memory-test path, and another unrelated PR also failed earlier on the same test.

Observed failing run on PR #21085:

• Commit: e8909a0fdc18078efb80f6613bef02c40ed90622
• Run: https://github.com/anomalyco/opencode/actions/runs/24022306588
• Failing job: unit (linux)
• Failing job URL: https://github.com/anomalyco/opencode/actions/runs/24022306588/job/70053527005

Relevant failing log excerpt:

• Baseline: 88.22 MB
• After 50 fetches: 142.01 MB
• Growth: 53.79 MB
• Expected threshold in test: < 5 MB

Another unrelated PR also failed on the same test:

• Run: https://github.com/anomalyco/opencode/actions/runs/24021334874
• Same unit (linux) test failed with:
  • Baseline: 108.71 MB
  • Growth: 63.08 MB
  • memory: abort controller leak > webfetch does not leak memory over many invocations

The same PR later passed on re-run:

• Commit: 02145f23f579d7523d9d1980be9e49c3de07014c
• Run: https://github.com/anomalyco/opencode/actions/runs/24022923003
• Passing unit (linux) job: https://github.com/anomalyco/opencode/actions/runs/24022923003/job/70055338429

Additional context:

• packages/opencode/src/util/abort.ts already uses controller.abort.bind(controller).
• The companion test compare closure vs bind pattern directly was still passing in the failing runs.
• The reporting branch did not modify packages/opencode/src/tool/webfetch.ts, packages/opencode/src/util/abort.ts, or packages/opencode/test/memory/abort-leak.test.ts.

Plugins

None

OpenCode version

opencode package version in repo: 1.3.15

Steps to reproduce

1. Open a PR against anomalyco/opencode and let the test workflow run.
2. Watch the unit (linux) job in .github/workflows/test.yml.
3. On intermittent failing runs, the failure appears in packages/opencode/test/memory/abort-leak.test.ts on memory: abort controller leak > webfetch does not leak memory over many invocations.
4. Re-run the failed job or workflow. In at least one observed case, the same logical change later passed without code changes to the memory-test path.

Screenshot and/or share link

Failing run:

• https://github.com/anomalyco/opencode/actions/runs/24022306588

Passing re-run:

• https://github.com/anomalyco/opencode/actions/runs/24022923003

Operating System

GitHub Actions Linux runner: blacksmith-4vcpu-ubuntu-2404 / Ubuntu 24.04 environment

Terminal

bash in GitHub Actions runner

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. This project requires one of the three official templates: Bug Report, Feature Request, or Question. This appears to be a bug report, which requires a Description field with real content and some context about how to reproduce the issue.
• Please resubmit using the Bug Report template, including system information (OS, version, environment) to help maintainers reproduce or investigate the intermittent CI failure.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue! It now follows our contributing guidelines with a clear description, reproduction steps, version info, and OS/environment details. The compliance label has been removed.