❔ Need help analyzing a dotMemory snapshot
I have a dotMemory snapshot of my application with information about a memory leak, but I don't have access to certain features of dotMemory (such as GC roots and reference tracing) due to being on Linux. I could really use some help analyzing this dump and get a second opinion on where to focus my efforts in removing the memory leak. As far as I can tell, an expensive serialization operation creates a large amount of string data (
BsonString and System.String) that gets promoted to the gen2 heap, where it then sits forever.
The leak is not in my own code, as this application is built on assemblies from a VR game (it's essentially a mod, allowed under their mod policy), but fixing it is doable through runtime patching with Harmony. All I really need is to identify where and why the problematic objects in question are being kept alive.1 Reply
Looks like nothing has happened here. I will mark this as stale and this post will be archived until there is new activity.