Hi, I’m trying to optimize my code to run faster, and callgrind is revealing thousands of calls to a class Destructor. These are completely unexpected, as I only allocate these objects a few times in the program, and their lifetime is supposed to be quite long. I’m wondering if an expert with more ability in decyphering callgrind output can assist.
I’ve attached the output of callgrind_annotate --auto=yes, gzipped because it’s quite lengthy.
I’ve also used kcachegrind to look at the analysis, it seems to be correct: MyInterpolator::~MyInterpolator is called many times by inside different functions (including ROOT library functions). This leads me to think that it’s ROOT’s garbage collection at play?
Thanks, if I need to provide other information about my code, I can definitely do that. Unfortunately a “minimal example” will probably not be possible.
Yes, something is broken; valgrind thinks that R__unzip calls textinput (i.e. the prompt handling). Wrong.
Is this on MacOS? (I see MachO being mentioned.) valgrind doesn’t really work on MacOS. Please repeat on Linux and send the output - that should make more sense. Or use the XCode Profiler and send a sample file.
Yes this is on OSX. I knew valgrind didn’t work on 10.9 until recently, but with the latest versions it would install even through my package manager. I didn’t realize it was installable but not really working properly.
I redid the profiling with the XCode “instruments” program, and indeed the spurious calls are gone, so I’m guessing they were never really there in the first place. I was able to track down some minor memory leaks and further optimize my program.