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
I fixed the most egregious memory leak in Netdriver here.
However, the interplay between the threading Tasks in NetMainLoop and NetEvents is horrifically complex and I'm not sure I got it right. I'd really appreciate a thorough code review by you.
In addition, there still is a very weird memory leak (or allocation of objects that doesn't make sense):
Set "Application.UseSystemConsole": true in ./UICatalog/bin/Debug/net7.0/.tui/UICatalog.config
{
"Application.UseSystemConsole" : true
}
Start Performance Profiler with memory profiling on
Take a snapshot right away
Double click on "Generic"
Hit ESC to close Generic
Take a snapshot
You'll see something like this:
Click on the +1612 and see this (sort by "Count Diff"):
For some reason ~1000 "Task+DelayPromiseWithCancellation" objects are being created. The number is different each run, but not in an deterministic way. I've also noticed that it has something do with mouse vs. keyboard input. But I've not been able to find a pattern. Nor have I figured out how to fix it (obviously).
@BDisp,
I fixed the most egregious memory leak in Netdriver here.
However, the interplay between the threading Tasks in
NetMainLoop
andNetEvents
is horrifically complex and I'm not sure I got it right. I'd really appreciate a thorough code review by you.In addition, there still is a very weird memory leak (or allocation of objects that doesn't make sense):
./UICatalog/bin/Debug/net7.0/.tui/UICatalog.config
You'll see something like this:
Click on the +1612 and see this (sort by "Count Diff"):
For some reason ~1000 "Task+DelayPromiseWithCancellation" objects are being created. The number is different each run, but not in an deterministic way. I've also noticed that it has something do with mouse vs. keyboard input. But I've not been able to find a pattern. Nor have I figured out how to fix it (obviously).
Maybe you can see what's going on?
Originally posted by @tig in #2885 (comment)
The text was updated successfully, but these errors were encountered: