w3c / w3c/ServiceWorker

Size limits with synchronous WebAssembly functions

Open
#1,499 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
3.6k
Forks
324
Avg merge
14d 22h
Merged PRs (30d)
1

Description

Right now the synchronous new WebAssembly.Module(foo) / new WebAssembly.Instance(foo, bar) functions have a 4 KB size limit on the main thread, because they block the event loop.

However, you can use them in regular workers without the 4 KB limit.

Should they be allowed in service workers with or without the 4 KB limit?

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 Service Worker specification sections governing WebAssembly and synchronous execution, then compare the stated 4 KB behavior in the main thread with regular workers. The work is done when the service-worker behavior and any size limit are decided and reflected in the specification.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, wasm
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.