You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the WASM memory is just a huge array buffer.
We need a way (extensibility point? + contribution of .NET Runtime team?) to inspect the .NET WASM memory.
Currently the most common scenario is Blazor WebAssembly application running in browser.
It is currently impossible to diagnose memory leaks or proceed with any other in-depth analysis of the memory.
AB#46073118
The text was updated successfully, but these errors were encountered:
.NET for Wasm already has a tool to analyze memory (we integrated that in Uno Platform). I'd guess that the .NET will make this working in the main branch sooner or later :)
In the end, I would like to see the ability to examine browser heap snapshots in a similar way the SOS.dll (dotnet-dump analyze) allows us on other platforms.
Currently, the WASM memory is just a huge array buffer.
We need a way (extensibility point? + contribution of .NET Runtime team?) to inspect the .NET WASM memory.
Currently the most common scenario is Blazor WebAssembly application running in browser.
It is currently impossible to diagnose memory leaks or proceed with any other in-depth analysis of the memory.
AB#46073118
The text was updated successfully, but these errors were encountered: