I’ve found semi black box fuzzing to be helpful as well. Spam the process with requests, wait to observe leak, start bisecting source, etc., repeat. Throw a while (1000) around some supposedly allocation neutral code blocks.
The third type from the article is memory fragmentation between a VM and an OS due to lazy freeing of unused memory by the VM. This is quite different from the common meaning of fragmentation which describes having free memory fragments across non-continuous blocks of physical memory.
I’ve found semi black box fuzzing to be helpful as well. Spam the process with requests, wait to observe leak, start bisecting source, etc., repeat. Throw a while (1000) around some supposedly allocation neutral code blocks.
tl;dr: memory leaks, space leaks, and fragmentation
The third type from the article is memory fragmentation between a VM and an OS due to lazy freeing of unused memory by the VM. This is quite different from the common meaning of fragmentation which describes having free memory fragments across non-continuous blocks of physical memory.