Repository navigation
[wasm][R2R] b68872 collides with first-pass ExInfo #133468
Description
Description
JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b68872 asserts during an exception filter in the browser-wasm CoreCLR ReadyToRun lane.
Reproduction Steps
Run the runtime-wasm-non-libtests pipeline with ReadyToRun tests enabled on dotnet/runtime commit ef1850bdc9e7d142888247d9bb5df3b74a7ae341 (Azure DevOps build 1588226, Helix job 2a25b357-0ff1-40a2-9fe9-5e205f73cb27, work item Regression_6).
Expected behavior
The test completes its exception-filter checks with exit code 100.
Actual behavior
Running test: JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b68872/b68872/b68872.dll
inside 1st filter
Assert failure(PID 42 [0x0000002a], Thread: 1 [0x0001]): did not expect to collide with a 1st-pass ExInfo during a EH stackwalk
File: /__w/1/s/src/coreclr/vm/exceptionhandling.cpp:4273
Aborted(native code called abort())
RuntimeError: unreachable
Regression?
Unknown. This was reproduced on current main during the #133305 census.
Known Workarounds
Exclude only this IL project from browser CoreCLR ReadyToRun execution. Other Regression_6 tests and non-R2R configurations remain enabled.
Configuration
- dotnet/runtime commit
ef1850bdc9e7d142888247d9bb5df3b74a7ae341 - CoreCLR browser-wasm
- Checked runtime
- ReadyToRun / crossgen2
- Node.js 23.11.1
Other information
Tracking issue: #133305.
Note
This issue was authored with GitHub Copilot.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
dotnet-policy-service commentedon Sep 9, 2026
Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Sep 9, 2026
Tagging subscribers to this area: @dotnet/crossgen-contrib
See info in area-owners.md if you want to be subscribed.
lewing commentedon Sep 15, 2026
#133932 has fix
Fix Wasm R2R exceptions escaping filters (#133932)
Fix Wasm R2R exceptions escaping filters (dotnet#133932)