Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Reset the browser worker startup timeout after WASM loads

Open
  • Is something wrong?
#1,049 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
wasm
Domain
web-dev

Research direction

Locate the browser worker startup timeout and trace the WASM loading and runtime-construction phases described in the issue. Verify that each phase has its own deadline and that a worker is not terminated immediately after reporting loaded while runtime construction is still active.

Written by the indexing model from the issue text.

Description

Safari can spend most of the 30-second worker startup timeout loading and compiling WASM. The same timeout also covers runtime construction, so a worker can report loaded and still be terminated moments later.

Treat the timeout as per-phase inactivity by giving WASM loading and runtime construction separate deadlines.

Dominant language
Swift
Stars
10
Forks
3
Avg merge
1d 9h
Merged PRs (30d)
211

Getting set up

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 paritytech/host-rust-core

All issues in paritytech/host-rust-core

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.