-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory - Ability to inspect .NET WebAssembly heap snapshot #32
Comments
.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. |
Thanks a lot for filing. Great feature request! |
cc @lewing |
Let me ping a few more people offline about this and report back if I learn anything new. |
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: