Closed Bug 2015877 (wasm-jspi-nightly) Opened 4 months ago Closed 1 month ago

Enable WebAssembly JS-PI in Nightly

Categories

(Core :: JavaScript: WebAssembly, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
152 Branch
Tracking Status
firefox152 --- fixed

People

(Reporter: rhunt, Assigned: rhunt)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-complete)

Crash Data

Attachments

(3 files)

Tracking bug for flipping on JS-PI in Nightly.

Summary: Enable WebAssembly js-promise-integration in Nightly → Enable WebAssembly JS-PI in Nightly
Alias: wasm-jspi-nightly

Once it's enabled, it should probably be added to https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features and be mentioned in the Nightly release notes.

Sebastian

Keywords: dev-doc-needed
  • Extend getBuildConfiguration to report what's compiled in the binary.
  • Ensure we're feature testing everything that's compiled in.
  • Move to directiveless so we can assume no experimental flags were added
    by a jit-test directive.
  • Normalize the relaxedSIMD name to simplify the test.
Assignee: nobody → rhunt
Status: NEW → ASSIGNED

Don't force enable stack-switching when we enable JS-PI, instead
only enable it for the builtin modules that JS-PI internally uses.

Pushed by rperta@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/82e4b736deff https://hg.mozilla.org/integration/autoland/rev/2a636a0ba55f Revert "Bug 2015877 - wasm: Enable JS-PI in nightly. r=yury,webidl,dom-worker-reviewers,smaug,asuth" for causing mochitest failures at test_worker_interfaces.html

Backed out for causing mochitest failures at test_worker_interfaces.html
Backout link
Push with failures
Failure log(s)

Flags: needinfo?(rhunt)
Flags: needinfo?(rhunt)
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch

This causes wasm crashes such as bp-2dc78c16-94c6-414c-a153-8d5f90260506. Code sheriffs will revert the changes to resolve the issue with the next Nightly.

Crash Signature: [@ std::exchange]
Pushed by sstanca@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/c90c4a59e34b https://hg.mozilla.org/mozilla-central/rev/249aec08cc0d Revert "Bug 2015877 - wasm: Enable JS-PI in nightly. r=yury,webidl,dom-worker-reviewers,smaug,asuth" as requested by @aryx for causing wasm crashes.

Reverted this as requested by @aryx for causing wasm crashes.

Status: RESOLVED → REOPENED
Flags: needinfo?(rhunt)
Resolution: FIXED → ---
Target Milestone: 152 Branch → ---

Looks like that website was feature-detecting JS-PI and started running it in Nightly once it was enabled.

Their code ran into a bug in the wasm bytecode we internally emit, which was caught by our validator and turned into a crash. I have a fix to handle it. I verified that website no longer crashes.

Flags: needinfo?(rhunt)
Status: REOPENED → RESOLVED
Closed: 1 month ago1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch
Type: task → enhancement

Is this something you wanted to call out in the Nightly release notes? Please add a relnote-firefox? nomination to the bug if yes.

Flags: needinfo?(rhunt)

Yes this is worth calling out in Nightly release notes (didn't know we had had Nightly only release notes). I was planning on the main release notes when we let it ride the trains (either this release or next).

Release Note Request (optional, but appreciated)
[Why is this notable]: New WebAssembly feature the helps porting applications to the Web.
[Affects Firefox for Android]: Yes
[Suggested wording]: Enabled the WebAssembly JS-Promise-Integration proposal in Nightly.
[Links (documentation, blog post, etc)]: https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md

relnote-firefox: --- → ?
Flags: needinfo?(rhunt)

Added to the Fx152 nightly release notes, please allow 30 minutes for the site to update.
The nightly-only note will be removed after three cycles or when it is enabled by default, whichever comes earlier.

QA Whiteboard: [qa-triage-done-c153/b152]

Docs for 152: We've just added a release note for now.

We are documenting the feature properly for 153, with docs work being tracked in https://github.com/mdn/content/issues/44468 / https://bugzilla.mozilla.org/show_bug.cgi?id=2044809

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: