Valgrind is giving me a memory leak when I call DcmSegmentation::loadDataset. Here is the output from "valgrind --leak-check=full".
This is on DCMTK version v3.6.1, 2015-09-24, running on Ubuntu 16.04. Here is the relevant code:==18910== 954,134 (1,944 direct, 952,190 indirect) bytes in 1 blocks are definitely lost in loss record 1,522 of 1,522
==18910== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==18910== by 0x603D3A9: DcmSegmentation::loadDataset(DcmDataset&, DcmSegmentation*&) (in /usr/lib/libdcmseg.so.3.6.1.abi2)
Code: Select all
DcmFileFormat fileFormat;
const char *dsoPath = dso.name();
OFCondition status = fileFormat.loadFile(path);
DcmDataset *dso_data = fileFormat.getDataset();
// Initialize the DcmSegmentation object
DcmSegmentation *dcmSegmentation;
status = DcmSegmentation::loadDataset(*dso_data, dcmSegmentation);