Finding memory leaks in your #dotnet applications with #dotMemory be like.
Conversation
Notices
-
Embed this notice
Khalid ⚡️ (khalidabuhakmeh@mastodon.social)'s status on Wednesday, 04-Sep-2024 10:26:06 JST Khalid ⚡️ -
Embed this notice
Khalid ⚡️ (khalidabuhakmeh@mastodon.social)'s status on Wednesday, 04-Sep-2024 10:26:04 JST Khalid ⚡️ @simoncropp @dHeinemann nah it's just common practice of using a list as a quick and dirty cache but forgetting to implement the invalidation part of the cache. 😅
Paul Cantrell repeated this. -
Embed this notice
Simon Cropp (simoncropp@hachyderm.io)'s status on Wednesday, 04-Sep-2024 10:26:04 JST Simon Cropp @khalidabuhakmeh @dHeinemann its that old saying: programming is like a murder mystery where you are the victim, the murderer, and the detective
-
Embed this notice
Dave Heinemann 🇦🇺 (dheinemann@fosstodon.org)'s status on Wednesday, 04-Sep-2024 10:26:05 JST Dave Heinemann 🇦🇺 @khalidabuhakmeh I don't recall having memory leaks with List<T> before. What's the problem? Objects not being garbage collected because a long-lived List<T> still holds a reference?
-
Embed this notice
Simon Cropp (simoncropp@hachyderm.io)'s status on Wednesday, 04-Sep-2024 10:26:05 JST Simon Cropp @dHeinemann @khalidabuhakmeh i am also curious
-
Embed this notice