Closed Bug 1884148 Opened 1 year ago Closed 4 months ago

Ship the Atomics.waitAsync proposal

Categories

(Core :: JavaScript Engine, task, P2)

task

Tracking

()

RESOLVED FIXED
145 Branch
Tracking Status
relnote-firefox --- 145+
firefox145 --- fixed

People

(Reporter: dminor, Assigned: dminor)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-complete, webcompat:platform-bug)

Attachments

(2 files)

This is to track shipping the Atomics.waitAsync proposal once it's been implemented.

Severity: -- → N/A
Priority: -- → P2
Keywords: dev-doc-needed

This just landed in Firefox 140, we should wait a few releases before shipping.

Assignee: nobody → dminor
Status: NEW → ASSIGNED
Pushed by chorotan@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/2e7f7f9a115c https://hg.mozilla.org/integration/autoland/rev/b5ae55d36d5d Revert "Bug 1884148 - Ship the Atomics.waitAsync proposal; r=mgaudet" for causing wpt failures on atomics-wait-async.https.any.html

Backed out for causing wpt failures

Backout link

Push with failures

Failure log

Flags: needinfo?(dminor)
Flags: needinfo?(dminor)
Pushed by chorotan@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/0f6d18cdcce6 https://hg.mozilla.org/integration/autoland/rev/b19bd9e4f248 Revert "Bug 1884148 - Handle eJSTimeout in GetTimeoutReasonString and update wpt expectations; r=dom-worker-reviewers,asuth" for causing wpt failures on Mutex_posix.cpp

Backed out for causing wpt failures

Backout link

Push with failures

Failure log

Flags: needinfo?(dminor)

I've filed Bug 1980271 to investigate the tsan failure, I see Atomics.waitAsync on the stack, so it's quite possibly a bug in our implementation.

Depends on: 1980271
Flags: needinfo?(dminor)
Pushed by amarc@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/0df3b92e27d9 https://hg.mozilla.org/integration/autoland/rev/fd9ad3129f48 Revert "Bug 1884148 - Handle eJSTimeout in GetTimeoutReasonString and update wpt expectations; r=dom-worker-reviewers,asuth" for causing wpt failures @ integration-with-the-javascript-agent-formalism/atomics-wait-async.https.any.worker.html

Backed out for causing wpt failures @ integration-with-the-javascript-agent-formalism/atomics-wait-async.https.any.worker.html

Flags: needinfo?(dminor)
Depends on: 1984739

Ugh, this is similar to bug 1980271.

Opened bug 1984739.

Thanks for having a look Iain :)

Flags: needinfo?(dminor)
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 145 Branch

Should that be included in our 145 release notes? Thanks

Flags: needinfo?(dminor)

Release Note Request (optional, but appreciated)
[Why is this notable]: Adds support for Atomics.waitAsync, which is implemented in Safari and Chromium, and has caused webcompat problems for us.
[Affects Firefox for Android]: Yes
[Suggested wording]: Support has been added for the Atomics.waitAsync proposal, which is a non-blocking, asynchronous version of Atomics.wait. This allow synchronization of threads based upon the value in a shared memory location, for more details please see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/waitAsync.
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/waitAsync

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

Thanks, note added to our 145 nIghtly release notes. I am keeping the relnote? tracking flag open until we ship 145 and integrate this note into our final release notes.

QA Whiteboard: [qa-triage-done-c146/b145]

FF145 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/41498

Added to our final 145 release notes.

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

Attachment

General

Created:
Updated:
Size: