Hi Adrian, no worries, a data node just references its data (in this case the image). mitk::Image is more or less just a wrapper for an itk::Image so there shouldn't be a double allocation neither. However, the memory usage indicator of the MITK Workbench does not "accurately" report the current memory usage (which is an annoying issue), hence you shouldn't trust it. ;-) I guess the memory usage indicator just shows the triple size of the image data due to two *temporary* copies of the image data which were already released after the actual loading/first rendering or something similar.
Best, Stefan PS: Sent again, since I forgot to "reply to all". ________________________________________ Von: Adrian Li [[email protected]] Gesendet: Mittwoch, 12. November 2014 08:59 An: [email protected] Cc: Chenming; Chenxiaoqing Betreff: [mitk-users] Memory allocation problem(triple size of real data allocated) Dear List, When I load a dicom image and try to display it I found MITK allocating triple size of real data in platform. For instance, I read an image with size 10M but this action actually occupies 50M of system. I think one for mitk::image, one for mitk::datanode and another for the itk image. So I wanna ask what strategy I can use to allocate the memory only once? Best, Adrian ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
