On my research list: FastMM4 LogAllocatedBlocksToFile to help find pseudo “leaks”: allocations released at application end, but during run-time progressively increase memory usage
Posted by jpluimers on 2018/08/01
From a quick scan for LogAllocatedBlocksToFile, I found these links I need to dig deeper into:
- [WayBack] http://tech.turbu-rpg.com/486/wanted-live-leak-detection-for-fastmm
- [WayBack] EurekaLog blog: Catching memory leaks, redux
- [WayBack] Source: delphi – Knowing where memory is being allocated using FastMM – Stack Overflow
This in oder to spot “leaks” at run-time that are being release at process end, but build up memory usage over time. Some might call them “live leaks”.
Basically this is a technique I used a long time ago when I wrote a memory allocation dumper and parsing tool combination in the Turbo/Borland Pascal era called “Korsakov” (I might even have updated that to Delphi 1 once, but soon in Delphi better tools became available).
Another tool that might help here is [WayBack] GitHub – yavfast/dbg-spider: Spider – Delphi profiler with docs at [WayBack] Spider – Delphi profiler:
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment