[Insight-users] ImageSeriesReader memory allocation for large datasets

[Jesús Spí­nola]

Hi,

I've experienced the same problem Marius reported. When I try to open a
large volume with itk::ImageSeriesReader on windows XP it fails allocating
memory when there's enough system memory available.

I've tried to load several large volumes (400-600Mb) on the same system with
2 Gb of RAM under linux and windows vista, and I didn't have any problem,
but under windows xp they give me allocation failures ( all tried OS
versions were 32 bit ) so it seems it is a windows xp problem with memory
management.

Did someone find any solution for this problem? Is there some workaround to
avoid this lack of memory on windows xp?

Any hint would be very apreciatte.

On Tue, May 6, 2008 at 9:59 AM, Hauke Heibel <heibel at cs.tum.edu> wrote:

> Hi,
>
> I once have had similar experiences. You need to check a few more things.
> Additional memory might be required, when your program needs to convert the
> data (unsigned short != short, etc.). Note, that this might happen inside
> the ImageSeriesReader. From what I remember, the ImageSeriesReader requires
> in the best case (without any conversion)
>
> sizeof(volume) + 2*sizeof(biggest slice)
>
> In your case this does not change much. You also need to make sure, that
> the previous part of your program did not consume too much memory. You might
> want to take a look at the Process Explorer (
> http://www.microsoft.com/germany/technet/sysinternals/utilities/ProcessExplorer.mspx).
> It will give you detailed information on the process that is running
> including very good information about the memory consumption. Maybe you can
> give a hint on the memory consumption before the allocation that failed.
>
> I hope that helps a bit,
> Hauke
>
> Marius Erdt wrote:
>
>> Hi,
>>
>> I have tested some more data sets (.dcm, .png) on different systems, but
>> the result is always the same. As soon as the number of slices gets too
>> high, the memory allocation fails.
>>
>> Does anyone have an idea how this problem can be fixed?
>>
>> Thanks,
>>
>> Marius
>>
>>
>>
>> I added the output to the file and loaded a data set of 809 slices of
>> 16-Bit PNG images with a resolution of 573x330. This is the result:
>>
>> Number of pixels requested = 152973810
>> Bytes per pixel = 4
>>
>> so the size should be ~583 Mb in total. However, the memory could not be
>> allocated.
>>
>> regards,
>> Marius
>>
> --
> Tim Hauke Heibel
> Computer Aided Medical Procedures (CAMP)
> fon: +49 89 289 19427
> fax: +49 89 289 17059
>
>
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20080804/40fb06f6/attachment-0001.htm>