Wasm Integration cpp events lack debug ids

[Fwang36]

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

9.25.1

Framework Version

No response

Link to Sentry event

https://francisorg.sentry.io/issues/6660050003/?project=4509447755857920&query=is%3Aunresolved&referrer=issue-stream&stream_index=0

Reproduction Example/SDK Setup

Original user provided a repro and will be attached to linked Linear ticket

Steps to Reproduce

Repro contains a readme with instructions. Below are screenshots from my org after I ran the repro

Expected Result

CPP errors get symbolicated

Actual Result

CPP errors are not symbolicated -

Debug files with debug ids get uploaded -

Event only contains debug ids of JS source maps but not the uploaded wasm file leading to no mapping -

[Lms24]

Hi, just gonna leave a public comment as well. We asked @timfish to take a look at this and investigate further.

[timfish]

I haven't tested this yet but I've had a look through the supplied code.

It looks like the wasm is loaded via a script in the html. @sentry/wasm picks up debug meta information by patching the WebAssembly registration. This means it will only pick up debug ids for wasm files loaded after the Sentry SDK is initialised. If you can load the wasm after Sentry is initialised it should work!

[Fwang36]

Thanks! That works. I changed the load order and now the event's JSON shows the debug id for the .wasm file under debug_meta and the <unknown> frames are symbolicated.