Skip to content
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

Open
hakenr opened this issue Mar 30, 2022 · 5 comments
Open

Memory - Ability to inspect .NET WebAssembly heap snapshot #32

hakenr opened this issue Mar 30, 2022 · 5 comments
Labels
feature New feature or request tracked This issue is now tracked on our internal backlog

Comments

@hakenr
Copy link

hakenr commented Mar 30, 2022

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

@hakenr hakenr added the feature New feature or request label Mar 30, 2022
@jeromelaban
Copy link

.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 :)

@hakenr
Copy link
Author

hakenr commented Mar 30, 2022

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.

@captainbrosset
Copy link
Contributor

Thanks a lot for filing. Great feature request!
Let's ping @zoherghadyali to make sure this is on his radar.

@pavelsavara
Copy link

cc @lewing

@captainbrosset captainbrosset added the tracked This issue is now tracked on our internal backlog label Aug 21, 2023
@captainbrosset
Copy link
Contributor

Let me ping a few more people offline about this and report back if I learn anything new.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request tracked This issue is now tracked on our internal backlog
Projects
None yet
Development

No branches or pull requests

4 participants