Replay does not capture WebGPU canvas in 10.33.0

[aelhage]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

10.33.0

Framework Version

No response

Link to Sentry event

https://orthly-5a.sentry.io/explore/replays/745d3d684d83407ca8fdcb1342b5c38c/?environment=development&playlistEnd=2026-01-13T16%3A52%3A04&playlistStart=2025-12-14T16%3A52%3A04&project=4509017613860864&query=&referrer=replayList

Reproduction Example/SDK Setup

https://github.com/aelhage/sentry-webgpu

Steps to Reproduce

1. Modify code to use appropriate Sentry DSN
2. npm i
3. npm run start
4. Load localhost:1234

Expected Result

Canvas should be recorded as red/blue shape on a black background

Actual Result

Canvas is blank

Additional Context

• If @sentry/browser is downgraded to 10.32.1 in the sample repo, it successfully captures the canvas (replay)
• If the render and manual snapshot is only called once it successfully captures the canvas. It is only calling inside of the requestAnimationFrame callback that does not seem to work. (replay, branch)

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1458

[andreiborza]

Hi @aelhage, thanks for following up and filing this and apologies that the previous fix broke WebGPU replays.

I'll take a look.

[andreiborza]

@aelhage I think this is an issue with how WebGPU buffers are handled in conjunction with requestAnimationFrame.

I tried your reproduction repo (thanks for sharing btw!) and I start seeing the canvas contents when I use skipRequestAnimationFrame: true for the manual snapshot calls:

Sentry.getClient()
   ?.getIntegrationByName("ReplayCanvas")
   ?.snapshot(canvas, { skipRequestAnimationFrame: true });

Can you try with that?

[aelhage]

@andreiborza confirming that skipRequestAnimationFrame address the issue in the example repo, but I am still seeing the issue with our production app. I'll try to identify what difference is causing the issue and update the example repo if I'm able to. Thank you!