[vtkusers] memory allocation limit in windows 2000 or vtk ?

[John Biddiscombe]

David,

I don't know the real cause or solution, but I've had similar trouble doing operations on very large meshes. My best bet was that although my Ram + Virtual mem was large, the largest "continuous block" wasn't big enough and memory allocations failed. I tried increasing my virtual ram to 5GB, but it still failed, so I was left confused. I didn't find a solution and reimplemented one of my key algorithms to run on different inputs. I'm using win2k, but Borland C++ 6 (so it's an OS issue rather than compiler methinks)

JB

----- Original Message ----- 
From: "David Netherway" <david.netherway at adelaide.edu.au>
To: "vtk" <vtkusers at public.kitware.com>
Sent: Friday, August 09, 2002 2:08 AM
Subject: [vtkusers] memory allocation limit in windows 2000 or vtk ?


> Hello All,
> 
> I attempted to use vtkVolumeRayCastmapper on a volume of size 512x512x1011
> on a PC with 1.5Gb of RAM.
> 
> The program will successfully display raycast images if the shading is
> turned off. The memory usage is then about 1Gb. The program crashes when I
> turn on shading at the point where the EncodedGradientEstimator attempts to
> allocate (using new) another 0.5Gb RAM.
> 
> It seemed that either the virtual memory was not working or I had reached
> some allocation size limit. The compiler was visual c++ 7 (.net).
> 
> I tested the first by running the program twice, simultaneously, on an 800
> slice data set. This worked. The peak memory usage hit approximately 2.5Gb
> indicating that the virtual memory was working.
> 
> Does anyone have some suggestions as to what the problem might be?
> 
> Thanks, David
> 
> 
> _______________________________________________
> This is the private VTK discussion list. 
> Please keep messages on-topic. Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers