Aaron Hill 6e93927f63 web: Check for locked 'Player' mutex and reschedule with setTimeout ... We use 'wasm-bindgen-futures' as our futures executor on web, which in turn uses 'queueMicroTask'. This can result in the browser executing one of our futures while we're still inside our `requestAnimationFrame` callback (in particular, while we still have the `Player` mutex locked). We now detect this condition by attempting the lock the Player mutex inside of our `spawn_local` future. If this fails, we `await` a `setTimeout`-based promise, which ensures that our code runs in a new top-level `setTimeout` javascript 'task' (outside of our `requestAnimationFrame` callback).		2024-07-15 22:46:22 +02:00
..
src	web: Check for locked 'Player' mutex and reschedule with setTimeout	2024-07-15 22:46:22 +02:00
Cargo.toml	build(deps): bump the cargo-minor group with 3 updates	2024-07-09 00:42:31 +02:00