[wasm] System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose failing with WebSocketException

[elinor-fung]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1102265
Build error leg or test failing: System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose
Pull request: #117797

[19:19:09] info: [FAIL] System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose(server: wss://127.0.0.1:49187/WebSocket/EchoWebSocket.ashx)
[19:19:09] info: System.Net.WebSockets.WebSocketException : CloseOutputAsync_Client_InvalidPayloadData
[19:19:09] info:    at System.Net.WebSockets.BrowserWebSocket.ConvertResponse()
[19:19:09] info:    at System.Net.WebSockets.BrowserWebSocket.ReceiveAsyncCore(ArraySegment`1 buffer, CancellationToken cancellationToken)
[19:19:09] info:    at System.Net.WebSockets.Client.Tests.CloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose(Uri server)
[19:19:09] info: --- End of stack trace from previous location ---

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["CloseOutputAsync_ClientInitiated_CanReceive_CanClose", "CloseOutputAsync_Client_InvalidPayloadData"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1102265
Error message validated: [CloseOutputAsync_ClientInitiated_CanReceive_CanClose CloseOutputAsync_Client_InvalidPayloadData]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2025 2:54:02 AM UTC

Report

Build	Definition	Test	Pull Request
1150040	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#112876
1148555	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119599
1147873	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119702
1146219	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119628
1145755	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119584
1144762	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution
1144231	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#114969
1143909	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119518
1139630	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution
1137905	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119294
1135493	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#118932
1134226	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#117436
1131564	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution	#119069
1129101	dotnet/runtime	WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	5	14

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

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

[CarnaViire]

Note: Most of the test classes in System.Net.WebSockets.Client.Tests are renamed in PR #117255 to differentiate with the in-process loopback server. All test names remain the same. It should still be matched to the issue, if it were to fail in the future after #117255 is merged.

- System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose
+ System.Net.WebSockets.Client.Tests.CloseTest_Invoker_External.CloseOutputAsync_ClientInitiated_CanReceive_CanClose

[pavelsavara]

Why do we see close event earlier than the message event is processed ?

Maybe the implementation is wrong?

runtime/src/mono/browser/runtime/web-socket.ts

Lines 120 to 125 in be1ef91

	receive_promise_queue.drain((receive_promise_control) => {
	setI32(receive_status_ptr, 0); // count
	setI32(<any>receive_status_ptr + 4, 2); // type:close
	setI32(<any>receive_status_ptr + 8, 1);// end_of_message: true
	receive_promise_control.resolve();
	});

maybe we need to treat close event as another event and add it into event_queue.enqueue same way as data.