Atomics.wait()

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since December 2021.

The Atomics.wait() static method verifies that a shared memory location still contains a given value and if so sleeps, awaiting a wake-up notification or times out. It returns a string which is either "ok", "not-equal", or "timed-out".

Note: This operation only works with an Int32Array or BigInt64Array that views a SharedArrayBuffer, and may not be allowed on the main thread. For a non-blocking, asynchronous version of this method, see Atomics.waitAsync().

Syntax

js
Atomics.wait(typedArray, index, value)
Atomics.wait(typedArray, index, value, timeout)

Parameters

typedArray

An Int32Array or BigInt64Array that views a SharedArrayBuffer.

index

The position in the typedArray to wait on.

value

The expected value to test.

timeout Optional

Time to wait in milliseconds. NaN (and values that get converted to NaN, such as undefined) becomes Infinity. Negative values become 0.

Return value

A string which is either "ok", "not-equal", or "timed-out".

  • "ok" is returned if woken up by a call to Atomics.notify(), regardless of if the expected value has changed
  • "not-equal" is returned immediately if the initial value does not equal what is stored at index
  • "timed-out" is returned if a sleeping wait exceeds the specified timeout without being woken up by Atomics.notify()

Exceptions

TypeError

Thrown in one of the following cases:

RangeError

Thrown if index is out of bounds in the typedArray.

Examples

Using wait()

Given a shared Int32Array:

js
const sab = new SharedArrayBuffer(1024);
const int32 = new Int32Array(sab);

A reading thread is sleeping and waiting on location 0 because the provided value matches what is stored at the provided index. The reading thread will not move on until the writing thread has called Atomics.notify() on position 0 of the provided typedArray. Note that if, after being woken up, the value of location 0 has not been changed by the writing thread, the reading thread will not go back to sleep, but will continue on.

js
Atomics.wait(int32, 0, 0);
console.log(int32[0]); // 123

A writing thread stores a new value and notifies the waiting thread once it has written:

js
console.log(int32[0]); // 0;
Atomics.store(int32, 0, 123);
Atomics.notify(int32, 0, 1);

Specifications

Specification
ECMAScript Language Specification
# sec-atomics.wait

Browser compatibility

BCD tables only load in the browser

See also