Repository navigation
[wasm] Multiple runtime crashes, and asserts in System.Collections.Immutable.Tests #65335
Description
Hit on #63958 but the PR itself should be unrelated to this.
Starting: System.Collections.Immutable.Tests.dll
{}
RuntimeError: memory access out of bounds
at <anonymous>:wasm-function[218]:0x1a7d5
at <anonymous>:wasm-function[1699]:0x7c4c4
at <anonymous>:wasm-function[1698]:0x7c469
at <anonymous>:wasm-function[1734]:0x7e1e1
at <anonymous>:wasm-function[529]:0x371e6
at <anonymous>:wasm-function[8374]:0x1b64a1
at <anonymous>:wasm-function[8373]:0x1b635e
at <anonymous>:wasm-function[526]:0x37141
at <anonymous>:wasm-function[551]:0x37781
at <anonymous>:wasm-function[1541]:0x75c32
at <anonymous>:wasm-function[1540]:0x757a0
at <anonymous>:wasm-function[1525]:0x745c2
at <anonymous>:wasm-function[1524]:0x7411c
at <anonymous>:wasm-function[359]:0x2710e
at <anonymous>:wasm-function[327]:0x240cb
at <anonymous>:wasm-function[379]:0x28933
at <anonymous>:wasm-function[223]:0x1a857
at <anonymous>:wasm-function[169]:0x18b9f
at <anonymous>:wasm-function[168]:0xbccf
at <anonymous>:wasm-function[7732]:0x196d0d
at <anonymous>:wasm-function[1900]:0x83f79
at <anonymous>:wasm-function[1904]:0x845e0
at mono_wasm_invoke_method (<anonymous>:wasm-function[118]:0x991c)
at Module._mono_wasm_invoke_method (./dotnet.js:12:128850)
at Object.t.<computed> (./dotnet.js:3:4100)
at _call_method_with_converted_args (./dotnet.js:3:48191)
at call_method (./dotnet.js:3:47309)
at ./dotnet.js:3:49132
at mono_call_assembly_entry_point (./dotnet.js:3:49260)
at Object.mono_run_main (./dotnet.js:3:57765)
at Object.init (test-main.js:214:43)
at Object.onDotnetReady (test-main.js:153:17)
at finalize_startup (./dotnet.js:3:62585)
at mono_wasm_after_runtime_initialized (./dotnet.js:3:59479)
at callRuntimeCallbacks (./dotnet.js:12:17800)
at postRun (./dotnet.js:12:13708)
at doRun (./dotnet.js:12:145047)
at run (./dotnet.js:12:145204)
at runCaller (./dotnet.js:12:144684)
at removeRunDependency (./dotnet.js:12:14500)
at receiveInstance (./dotnet.js:12:16355)
at receiveInstantiationResult (./dotnet.js:12:16476)
Process v8 exited with 1
Activity
radical commentedon Feb 14, 2022
Another instance of a similar looking crash but running on nodejs, build, and log:
Hit on my debug #65178 (at 73c6e90), which is running each of the test libraries 6 times on helix.
radical commentedon Feb 14, 2022
Another failure with nodejs, on the same build:
radical commentedon Feb 14, 2022
Another with nodejs, build:
radical commentedon Feb 14, 2022
Another with nodejs, build:
radical commentedon Feb 14, 2022
@radekdoulik all of these are from https://dev.azure.com/dnceng/public/_build/results?buildId=1612165&view=logs&j=11c5c840-d20a-5536-428b-70d8cd9c6259&t=73598586-463f-5241-5dc8-b8ffdebf8b89
[-][wasm] interpreter crash `memory access out of bounds` in `System.Collections.Immutable.Tests`[/-][+][wasm] Multiple runtime crashes, and asserts in `System.Collections.Immutable.Tests`[/+]elinor-fung commentedon Feb 15, 2022
Marking blocking-clean-ci. A lot of PR builds are hitting this.
AaronRobinsonMSFT commentedon Feb 15, 2022
Hitting this in #65246
Test log
radical commentedon Feb 16, 2022
Getting a a different crash now on a rolling build:
V8:
chrome, which seems to be essentially the same crash:
Disable System.Collections.Immutable.Tests due to dotnet#65335
[wasm] Disable aot tests failing due to OOM (#65413)
radical commentedon Feb 17, 2022
Disabled the tests, so removing
blocking-clean-ci.[wasm] Re-enable tests that were disabled due to the earlier emsdk bump
radical commentedon Feb 18, 2022
This started with the 2.0.34 bump, which has been rolled back now.
elinor-fung commentedon Feb 20, 2022
@radical / @radekdoulik do you know what it was about the newer emscripten version that resulted in the assortment of failures?
[wasm] Emscripten 3.1.1 bump (#63894)