When the code is >10,000 lines of code (LoC), or >100,000 LoC, and we see memory of our research growing either slowly, or aggressively, it would eventually crash based on the compute profile used. The following steps can be used via windbg, gdb, and dotnet profiler for an incisive look to find the root cause without reading the entire codebase. We can think of this as a surgical intervention for super-quick turnaround and resolution, rather than, a way to defer cleaning-up bad codes after-the-fact.