I am currently in the process of hunting memory leaks in one special functionality of our 32-bit product. Unfortunately it is a very complex and long running process.
Doing some research on the internet, I found an old tool CDMatch which would at least give me a good idea, where we are losing some memory.
So after some tweaking I found a way to get a trace of a single, successful run of the wanted functionality. Regrettably the size of the trace file amounts to about 790 MB, which PowerBuilder itself and CDMatch are unable to open/handle.
When trying to open the file with the PowerBuilder internal "Profiling Trace View", PowerBuilder crashes without a warning.
Running CDMatch from within the IDE also does crash when hitting the maximum of allowed memory (about 1.7 GB). Even creating a 64-Bit executable and running the program does just consume lots and lots of memory using up all of my free disk space for swapping.
So my main question is, what would be the best approach to analyze such a huge trace file, when even PowerBuilder itself seems to run into memory problems?