Open DierkDroth opened 1 month ago
@jeromelaban I consider memory leaks one of the most serious issues in any software technology - I'm not sure what your perspective is though... and I'm actually surprised that there is no reaction whatsoever by the UNO team on my report/repo.
In particular I would like to know:
Thanks in advance for your attention on this serious issue.
Current behavior
This is in continuation of this discussion. To my surprise it actually was quite simple to create a repo which would demonstrate the problem and chase UNO WASM into an 'OutOfMemory' scenario.
I'll spare the memory profiling for the sake of simplicity. Attached repo should release memory properly between iterations, but apparently doesn't. Please start the solution in VS, take a look at the comments in MainPage.cs and run it as UNO WASM head. Make sure to open the browser console by F12.
What am I doing wrong there?
Minimal.zip
Expected behavior
No response
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
None
Environment
Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia
NuGet package version(s)
No response
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response