Test failure with message "MONO_WASM: Out of memory" on string constructor

[carlossanlop]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=977742
Build error leg or test failing: WasmTestOnChrome-ST-System.Private.Xml.Tests.WorkItemExecution
Pull request: #113306

Error Message

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

{
  "ErrorMessage": "MONO_WASM: Out of memory",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

• Log file 1: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-113306-merge-d46fc02f84ba4f4ca2/WasmTestOnChrome-ST-System.Private.Xml.Tests/1/console.fcd98af0.log?helixlogtype=result

• Output 1:

[00:27:43] info: Discovering: System.Private.Xml.Tests.dll (method display = ClassAndMethod, method display options = None)
[00:27:43] info: Discovered:  System.Private.Xml.Tests.dll (found 4774 of 4834 test cases)
[00:27:43] info: Starting:    System.Private.Xml.Tests.dll
[00:29:47] info: Finished:    System.Private.Xml.Tests.dll
[00:29:48] fail: MONO_WASM: Out of memory
   at System.String.Ctor(ReadOnlySpan`1 value)
   at System.Runtime.CompilerServices.DefaultInterpolatedStringHandler.ToStringAndClear()
   at Microsoft.DotNet.XHarness.TestRunners.Xunit.WasmXmlResultWriter.WriteOnSingleLine(XElement assembliesElement)
   at Microsoft.DotNet.XHarness.TestRunners.Xunit.ThreadlessXunitTestRunner.WriteResultsToFile(TextWriter writer, XmlResultJargon jargon)
   at Microsoft.DotNet.XHarness.TestRunners.Common.ApplicationEntryPoint.WriteResults(TestRunner runner, ApplicationOptions options, LogWriter logger, TextWriter writer)
   at Microsoft.DotNet.XHarness.TestRunners.Common.ApplicationEntryPoint.InternalRunAsync(ApplicationOptions options, TextWriter loggerWriter, TextWriter resultsFile)
   at Microsoft.DotNet.XHarness.TestRunners.Common.WasmApplicationEntryPointBase.RunAsync()
   at Microsoft.DotNet.XHarness.TestRunners.Xunit.WasmApplicationEntryPoint.Run()
   at WasmTestRunner.MainAsync(String[] args)
Error: Out of memory
    at ln (http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:27393)
    at tn.resolve_or_reject (http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:26948)
    at http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:175719
    at http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:175783
    at mr (http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:35574)
    at Mc (http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:175358)
    at do_icall (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[293]:0x20098)
    at do_icall_wrapper (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[221]:0x1d34b)
    at mono_interp_exec_method (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[212]:0xf14e)
    at interp_entry (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[286]:0x1fb3d)
    at interp_entry_static_0 (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[322]:0x20ce3)
    at wasm_native_to_interp_System_Private_CoreLib_System_Threading_ThreadPool_BackgroundJobHandler (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[184]:0xc9f4)
    at mono_background_exec (http://127.0.0.1:56720/_framework/dotnet.native.wasm:wasm-function[791]:0x4a02b)
    at Ko (http://127.0.0.1:56720/_framework/dotnet.runtime.js:3:56767)
    at callUserCallback (http://127.0.0.1:56720/_framework/dotnet.native.js:8:106478)
    at http://127.0.0.1:56720/_framework/dotnet.native.js:8:106746
[00:29:48] fail: [out of order message from the browser]: http://127.0.0.1:56720/_framework/dotnet.runtime.js 2:27392 
[00:29:48] fail: [out of order message from the browser]: http://bla/ - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
[00:29:48] info: WASM EXIT 1
[00:29:48] info: Waiting to flush log messages with a timeout of 120 secs ..
[00:29:48] fail: Application has finished with exit code TESTS_FAILED but 0 was expected
[00:29:48] fail: [out of order message from the browser]: https://foo/foo - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
[00:29:48] info: Closing 1 browser tabs before setting the main tab to config page and quitting.
XHarness exit code: 71 (GENERAL_FAILURE)

C:\helix\work\workitem\e>set EXIT_CODE=71 
----- end Thu 03/13/2025  0:29:54.08 ----- exit code 71 ----------------------------------------------------------

• Log file 2: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-113306-merge-d5da1db3d0b648eeb6/WasmTestOnFirefox-ST-System.Private.Xml.Tests/1/console.8c987fed.log?helixlogtype=result

• Output 2:

[23:11:44] info: Initializing dotnet version 10.0.0-ci commit hash 321c16c0839fc3c9c18d4fa4a3c5a5b335dbc391
[23:11:44] info: Using threadless Xunit runner
[23:11:44] info: Discovering: System.Private.Xml.Tests.dll (method display = ClassAndMethod, method display options = None)
[23:11:49] info: Discovered:  System.Private.Xml.Tests.dll (found 4774 of 4834 test cases)
[23:11:49] info: Starting:    System.Private.Xml.Tests.dll
1741821123829	addons.xpi	ERROR	System addon update list error SyntaxError: XMLHttpRequest.open: 'http://%(server)s/dummy-system-addons.xml' is not a valid URL.
[23:15:48] info: Finished:    System.Private.Xml.Tests.dll
JavaScript error: http://127.0.0.1:45045/_framework/dotnet.runtime.js, line 3: Error: Out of memory
[23:15:50] fail: MONO_WASM: Out of memory
                    at System.String.Ctor(ReadOnlySpan`1 value)
                    at System.Runtime.CompilerServices.DefaultInterpolatedStringHandler.ToStringAndClear()
                    at Microsoft.DotNet.XHarness.TestRunners.Xunit.WasmXmlResultWriter.WriteOnSingleLine(XElement assembliesElement)
                    at Microsoft.DotNet.XHarness.TestRunners.Xunit.ThreadlessXunitTestRunner.WriteResultsToFile(TextWriter writer, XmlResultJargon jargon)
                    at Microsoft.DotNet.XHarness.TestRunners.Common.ApplicationEntryPoint.WriteResults(TestRunner runner, ApplicationOptions options, LogWriter logger, TextWriter writer)
                    at Microsoft.DotNet.XHarness.TestRunners.Common.ApplicationEntryPoint.InternalRunAsync(ApplicationOptions options, TextWriter loggerWriter, TextWriter resultsFile)
                    at Microsoft.DotNet.XHarness.TestRunners.Common.WasmApplicationEntryPointBase.RunAsync()
                    at Microsoft.DotNet.XHarness.TestRunners.Xunit.WasmApplicationEntryPoint.Run()
                    at WasmTestRunner.MainAsync(String[] args)
                 ManagedError@mono_background_exec (http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:31561
                 ln@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:27393
                 an/<@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:26950
                 Mc</</<@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:175719
                 Mc</<@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:175783
                 mr@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:35574
                 Mc<@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:175360
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[3]:0x0
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[293]:0x20098
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[221]:0x1d34b
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[212]:0xf14e
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[286]:0x1fb3d
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[322]:0x20ce3
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[184]:0xc9f4
                 @http://127.0.0.1:45045/_framework/dotnet.native.wasm:wasm-function[791]:0x4a027)
                 Ko@http://127.0.0.1:45045/_framework/dotnet.runtime.js:3:56767
                 callUserCallback@http://127.0.0.1:45045/_framework/dotnet.native.js:8:106478
                 createDotnetRuntime/safeSetTimeout/createDotnetRuntime<@http://127.0.0.1:45045/_framework/dotnet.native.js:8:106762
[23:15:50] info: WASM EXIT 1
[23:15:50] info: Waiting to flush log messages with a timeout of 120 secs ..
[23:15:50] fail: Application has finished with exit code TESTS_FAILED but 0 was expected
[23:15:50] info: Closing 1 browser tabs before setting the main tab to config page and quitting.
1741821351702	Marionette	INFO	Stopped listening on port 44657
XHarness exit code: 71 (GENERAL_FAILURE)
/root/helix/work/workitem/e /root/helix/work/workitem/e
----- end Wed Mar 12 11:15:52 PM UTC 2025 ----- exit code 71 ----------------------------------------------------------

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=977742
Error message validated: [MONO_WASM: Out of memory]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/13/2025 2:52:42 PM UTC

Report

Summary

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

[dotnet-policy-service]

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

[lewing]

WriteOnSingleLine looks... like it uses a lot of memory...

[pavelsavara]

@oroztocil could you please have look ?

also we could just observe it for a while and close it if it doesn't produce more hits anymore

[pavelsavara]

Maybe this was fixed by my xharness changes ?

dotnet/xharness#1388
dotnet/xharness#1403