sorting the data by number of allocations breaks the call stack tree completely, see attached screenshot:
the frame void Worker::loadInput(void) has 1007016 inclusive allocations, but expanding it shows only items with very few allocations. Further down a frame for QCommandLineParser::QCommandLineParser has one internal allocation, but expanding it shows a completely unrelated frame from the Worker::parseFile with 1007012 allocations - those should be part of the loadInput frame above.
milostosic
commented
5 years ago
sorting the data by number of allocations breaks the call stack tree completely, see attached screenshot:
the frame
void Worker::loadInput(void)has 1007016 inclusive allocations, but expanding it shows only items with very few allocations. Further down a frame forQCommandLineParser::QCommandLineParserhas one internal allocation, but expanding it shows a completely unrelated frame from theWorker::parseFilewith 1007012 allocations - those should be part of theloadInputframe above.