3 ms·
Wow, I had never really appreciated the fact that people working in GCed languages had to deal with memory leaks. One of the things I enjoy in the limited time
by zwieback 15y ago
Wow, I had never really appreciated the fact that people working in GCed languages had to deal with memory leaks. One of the things I enjoy in the limited time I work away from C and C++ is not having to worry about memory leaks but I guess it can happen depending on the complexity of the system and what you're plumbing together.
I'm wondering, though, is there no way to point back at the code that did the allocation? We used to instrument our heap management routines to give us whatever info we need to figure out who the offending allocator is, e.g. functions, line numbers, thread IDs, etc.