This may not be very useful for you, but you can write your own malloc shell. In our special โdiagnosticโ assemblies, it stores a table of all outstanding distributions (including the file name and line number where the distribution occurred), and displays everything that was still outstanding at the time of exit. It also uses the words canary (to check for buffer overflows) and a combination of rewriting memory and blocking checksums after free and before reallocation (to check after-work usage).
If your product is large enough, it can be frustrating to find - replace your entire source, hoping for the best. Also, the development time for your own malloc shell is probably not insignificant. Doing a lot of heavy things like what I mentioned above probably also will not help solve your speed problem. However, writing your own shell can provide maximum flexibility.
source share