[wasm] Uncaught TypeError: Cannot set property 'loaded_cb' of null

[radekdoulik]

Example failure:

https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-53603-merge-6de2ebd21d9742fbb7/System.Formats.Asn1.Tests/console.bb96e0e6.log?sv=2019-07-07&se=2021-07-13T18%3A47%3A03Z&sr=c&sp=rl&sig=36IYks3qOtQFUosFFMbRsam3qAdumj%2Fj1yZSpK%2BAqHU%3D

It fails like this:

XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/BD940A69/w/AFF709B2/uploads/xharness-output --engine=V8 --engine-arg=--stack-trace-limit=1000 --js-file=runtime.js -- --run WasmTestRunner.dll System.Formats.Asn1.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[19:00:39] info: Starting chromedriver with args: --headless --incognito --enable-features=NetworkService,NetworkServiceInProcess --allow-insecure-localhost --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-component-extensions-with-background-pages --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI --disable-ipc-flooding-protection --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only
Starting ChromeDriver 84.0.4147.0 (ff714bcb10c3356b1b1b2819148507a34fa4b1f8-refs/heads/master@{#768968}) on port 33549
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[19:00:40] info: browser: Console websocket connected.
[19:00:41] info: Arguments: --run,WasmTestRunner.dll,System.Formats.Asn1.Tests.dll,-notrait,category=IgnoreForCI,-notrait,category=OuterLoop,-notrait,category=failing
[19:00:41] fail: [out of order message from the browser]: http://127.0.0.1:37793/runtime.js 234:26 Uncaught TypeError: Cannot set property 'loaded_cb' of null
[19:15:40] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

[ghost]

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

Issue Details

---

Example failure:

https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-53603-merge-6de2ebd21d9742fbb7/System.Formats.Asn1.Tests/console.bb96e0e6.log?sv=2019-07-07&se=2021-07-13T18%3A47%3A03Z&sr=c&sp=rl&sig=36IYks3qOtQFUosFFMbRsam3qAdumj%2Fj1yZSpK%2BAqHU%3D

It fails like this:

XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/BD940A69/w/AFF709B2/uploads/xharness-output --engine=V8 --engine-arg=--stack-trace-limit=1000 --js-file=runtime.js -- --run WasmTestRunner.dll System.Formats.Asn1.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[19:00:39] info: Starting chromedriver with args: --headless --incognito --enable-features=NetworkService,NetworkServiceInProcess --allow-insecure-localhost --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-component-extensions-with-background-pages --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI --disable-ipc-flooding-protection --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only
Starting ChromeDriver 84.0.4147.0 (ff714bcb10c3356b1b1b2819148507a34fa4b1f8-refs/heads/master@{#768968}) on port 33549
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[19:00:40] info: browser: Console websocket connected.
[19:00:41] info: Arguments: --run,WasmTestRunner.dll,System.Formats.Asn1.Tests.dll,-notrait,category=IgnoreForCI,-notrait,category=OuterLoop,-notrait,category=failing
[19:00:41] fail: [out of order message from the browser]: http://127.0.0.1:37793/runtime.js 234:26 Uncaught TypeError: Cannot set property 'loaded_cb' of null
[19:15:40] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Author:	radekdoulik
Assignees:	-
Labels:	arch-wasm, area-Codegen-AOT-mono
Milestone:	-

[ViktorHofer]

Happened again in https://dev.azure.com/dnceng/public/_build/results?buildId=1201983&view=ms.vss-test-web.build-test-results-tab&runId=36034448&resultId=170003&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab

[ghost]

@ViktorHofer the PR hasn't been merged yet. It is waiting for some final CI test to finish. Hopefully it will be merged soon. Thanks for pointing it out though