how to release 'new DcmFileFormat'

[hiterneol]

DcmFileFormat *dfile = new DcmFileFormat();
OFCondition cond =dfile->loadFile(dlg.GetFileName(), EXS_Unknown,EGL_withoutGL,DCM_MaxReadLength,(const E_FileReadMode)OFFalse);

But I can't release variable 'dfile' by delete, such as

delete dfile;
dfile = NULL;

if I don't release 'dfile', there will be memory leak, anybody can help me?

[Marco Eichelberg]

But I can't release variable 'dfile' by delete, such as
delete dfile;

Why not?

[cmasson]

Hi.

I am facing the same kind of problem when trying to build a multiframe dicom file.

1 - A DcmFileFormat object is created.
2 - A DcmPixelSequence object is created (with a DCM_PixelData tag).
3 - For each image, a DcmPixelItem object is created and inserted into the pixel sequence.
3 - A DcmPixeltem object is created to build an offset table ; that pixel item is inserted into the pixel sequence with prepend().
4 - The pixel sequence is inserted into the dataset of the DcmFileFormat object.
5 - The method save() of DcmFileFormat is called to create the file.
6 - "delete" is applied to the DcmFileFormat, the DcmPixelSequence and the set of DcmPixelItem.

Then the process crashes...

Is there anything wrong with that way? Thanks for any clue.

[Jörg Riesmeier]

After you've inserted the pixel item and pixel sequence, you should not delete these objects manually. So, in step 6 just omit the deletion of the DcmPixelSequence and the DcmPixelItem objects.

[cmasson]

Hello.

Thanks for your answer. However, even when I delete no other object than the DcmFileFormat object, the process crashes when ~DcmItem() is called.

[Marco Eichelberg]

Sounds like you need to work through your code with a memory debugger tool such as valgrind. There could be various reasons for the problem you describe, one being that an object created on the stack (and not on the heap) is inserted into the DcmFileFormat tree of objects somewhere.