News for hackers. Stuff that matters.
Re:Hunting down a C memory leak in a Go program by Matthias247 on Saturday October 16, 2021 @05:23PM (#28891673)
I think it depends on how much context you have. For apps where I have written most of the code its usally easy to think it through and review some code paths. However the situation is vastly different if you run 90% unfamiliar code, like it often happens in larger organizations where everyone only contributed a tiny part of things. When you run millions of lines of code in production it's not reasonable to review everything in order being able to fix it - you need to use hints and tools to narrow down the source of the issue. That can be logs, metrics, debugging tools, profilers, etc.

There are no comments on this comment yet.