[wasm][windows] System.Threading.Channels.Tests failing with `RuntimeError: table index is out of bounds` on v8, chrome, and node.

[runfoapp]

From the console.log of one of the hits:

[10:24:45] fail: [out of order message from the browser]: http://127.0.0.1:49179/dotnet.wasm 0:537565 Uncaught RuntimeError: table index is out of bounds
[10:39:36] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Actual individual issues:

• [wasm] remainder by zero crash in System.Threading.Channels.Tests, on browser #65245
• [wasm] runtime crashes in System.Threading.Channels.Tests #65337

https://runfo.azurewebsites.net/search/tests/?q=name%3A%22wasmtestonbrowser-system.threading.channels.tests+work+item%22+definition%3Aruntime-extra-platforms

Runfo Tracking Issue: WasmTestOnBrowser-System.Threading.Channels.Tests failing with 'table index is out of bounds'

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
1605729	runtime-extra-platforms	Rolling	net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnBrowser-Ubuntu.1804.Amd64.Open	console.log			runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	0	1

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

From the console.log of one of the hits:

[10:24:45] fail: [out of order message from the browser]: http://127.0.0.1:49179/dotnet.wasm 0:537565 Uncaught RuntimeError: table index is out of bounds
[10:39:36] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Runfo Tracking Issue: WasmTestOnBrowser-System.Threading.Channels.Tests failing with 'table index is out of bounds'

Build	Definition	Kind	Run Name

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	0	0

Author:	runfoapp[bot]
Assignees:	-
Labels:	arch-wasm, untriaged
Milestone:	-

[elinor-fung]

Similar issue in the normal-System.Threading.Channels.Tests run: https://runfo.azurewebsites.net/search/tests/?q=started%3A~7%20definition%3Aruntime-extra-platforms%20name%3A%22normal-system.threading.channels.tests%20work%20item%22
console.log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-7b19d91d284b4fe88c/normal-System.Threading.Channels.Tests/1/console.73d5771f.log?%3Fsv%3D2019-07-07%26se%3D2022-02-28T10%253A01%253A21Z%26sr%3Dc%26sp%3Drl%26sig%3DX%252BOpuhkJhKQnCIltCPkzdVZQqgB%252F2d8tUTcwdp7xM6A%253D

[elinor-fung]

The runfo tracking issue doesn't seem to be updating right now. This is the query that was used to create the issue: https://runfo.azurewebsites.net/search/tests/?q=name%3A%22wasmtestonbrowser-system.threading.channels.tests+work+item%22+definition%3Aruntime-extra-platforms

[pavelsavara]

I think this is wasm exported functions table.
But also I wonder how come Module.onAbort didn't stop it before timeout.