I looked into this a bit today. V8 doesn't wrap JS exceptions in a Wasm Exception object - they [optimize this at the catch-site](https://source.chromium.org/chromium/chromium/src/+/main:v8/src/wasm/graph-builder-interface.cc;l=1298;drc=82dff63dbf9db05e9274e11d9128af7b9f51ceaa). Some discussion on this here: * https://github.com/WebAssembly/exception-handling/pull/301#pullrequestreview-1991446741 * https://github.com/WebAssembly/exception-handling/pull/269 Anyway this can wait until Ryan is back in case we want to do more work here.
Bug 1915254 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I looked into this a bit today. V8 doesn't wrap JS exceptions in a Wasm Exception object - they [optimize this at the catch-site](https://source.chromium.org/chromium/chromium/src/+/main:v8/src/wasm/graph-builder-interface.cc;l=1298;drc=82dff63dbf9db05e9274e11d9128af7b9f51ceaa). Some discussion on this here: * https://github.com/WebAssembly/exception-handling/pull/301#pullrequestreview-1991446741 * https://github.com/WebAssembly/exception-handling/pull/269 Anyway this can wait until Ryan is back in case we want to do more work here. (The simplest fix is probably to do the exception-wrapping in the realm of the instance that catches the exception.)