[wasm-ep] Wasm.Browser.EventPipe.Sample fails

[simonrozsival]

The Wasm.Browser.EventPipe.Sample fails when wasm perf tracing is enabled. The process gets stuck and the test timeouts.

Console output:

ChromeDriver was started successfully.
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: MONO_WASM: starting the diagnostic server url: ws://localhost:8088/diagnostics
[11:05:20] fail: Tests timed out. Killing driver service pid 31951
[11:05:20] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Full console log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-74410-merge-b99b2cf8b7b548de87/Wasm.Browser.EventPipe.Sample/1/console.4158a01b.log?helixlogtype=result

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

---

The Wasm.Browser.EventPipe.Sample fails when wasm perf tracing is enabled. The process gets stuck and the test timeouts.

Console output:

ChromeDriver was started successfully.
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4:42242 "MONO_WASM: afterLoadWasmModuleToWorker added message event handler" Worker
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: http://127.0.0.1:46767/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[10:50:29] info: MONO_WASM: starting the diagnostic server url: ws://localhost:8088/diagnostics
[11:05:20] fail: Tests timed out. Killing driver service pid 31951
[11:05:20] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Full console log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-74410-merge-b99b2cf8b7b548de87/Wasm.Browser.EventPipe.Sample/1/console.4158a01b.log?helixlogtype=result

Author:	simonrozsival
Assignees:	-
Labels:	arch-wasm
Milestone:	8.0.0