[vtkusers] VTK+ Bad Memory Allocation

[Alex Southern]

Ah ha,

This is something else I was wondering about.

No, I am using 64-bit windows, however I am compiling the application as 
a 32 bit process, I am in the process of rectifying this. (turns out the 
64-bit Compiler is not installed as standard in VS2008 Pro on a 64-bit 
machine!).

Whats the limit on 64-bit windows?

[Back to VTK] I have a suspicion that while this may be a limiting 
factor, it does not explain why altering the renderwindow size affects 
the memory allocation?

Cheers
Alex

On 13.4.2011 2:22, John Drescher wrote:
> On Tue, Apr 12, 2011 at 6:51 PM, Alex<mrapsouthern at gmail.com>  wrote:
>> Hi,
>>
>> I realise this is not a greatly detailed explanation of the problem but I
>> thought I'd see if this rings any bells with anyone first....
>>
>> Basically, my application makes large dynamic memory allocations (using
>> new), I find that I get seemingly random bad allocation errors. These
>> allocations are of type int.
>>
>> When I make the VTK renderwindow small, the allocation errors stop, (or at
>> least they do not occur for the same allocation size)
>>
>> The memory allocations have nothing to do with the VTK pipeline.
>>
>> If anyone has any information about memory issues vs. VTK i'd appreciate it.
>>
> Are you using 32 bit windows? Remember that will be limited to 1.2GB
> to 1.5GB max allocation size of the 2GB address space unless you
> activate /LARGEADDRESSAWARE and boot with the /3GB switch.
>
>