[wasm][debugger] Tests: Spawn MonoProxy in a separate process to avoid excessive memory usage for tests

[radical]

Some debugger test runs randomly get aborted on CI. See #89409

Running GetPropertiesTests in codespaces reveals that the RES memory usage of the process keeps increasing, reaching ~10G in 5mins. This suggests a memory leak.

Looking at the test process with dotnet dotnet-counters monitor --refresh-interval 1 -p ...:

One potential solution, and a good thing to do anyway would be to spawn MonoProxy in a separate process, for which we already have wrappers. Right now, we instantiate MonoProxy for each test in the same test process which is overkill and not representative of user scenarios.

relevant code

runtime/src/mono/wasm/debugger/DebuggerTestSuite/ChromeProvider.cs

Lines 92 to 97 in 4cb123a

	_debuggerProxy = new DebuggerProxy(loggerFactory, loggerId: Id, options: options);
	TestHarnessProxy.RegisterNewProxy(Id, _debuggerProxy);
	var browserUri = new Uri(con_str);
	WebSocket? ideSocket = await context.WebSockets.AcceptWebSocketAsync().ConfigureAwait(false);
	await _debuggerProxy.Run(browserUri, ideSocket, cts).ConfigureAwait(false);
	}

cc @thaystg @ilonatommy

[ghost]

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

Issue Details

---

Some debugger test runs randomly get aborted on CI. See #89409

Running GetPropertiesTests in codespaces reveals that the RES memory usage of the process keeps increasing, reaching ~10G in 5mins. This suggests a memory leak.

Looking at the test process with dotnet dotnet-counters monitor --refresh-interval 1 -p ...:

One potential solution, and a good thing to do anyway would be to spawn MonoProxy in a separate process, for which we already have wrappers. Right now, we instantiate MonoProxy for each test in the same test process which is overkill and not representative of user scenarios.

cc @thaystg @ilonatommy

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	9.0.0