[vtkusers] How to overcome the memory allocation problem.

[James Johnston]

You might want to consider rewriting in something else more modern.  If
that's too much work, then maybe you can write an external Visual C++ 64-bit
program that reduces the data set to something more manageable and then
sends it to your 32-bit program via some kind of inter-process communication
(e.g. named pipes)?

My experience is that trying to malloc anything more than a few tens of
megabytes in a 32-bit process is just asking for trouble - especially if
there's other stuff going on in that process.  The address space just gets
too fragmented.  Plus, you never know if there will be a few random,
poorly-based 3rd-party DLLs loaded right in the middle of your address space
to fragment it even more.

They do have a new C++ Builder XE3 64-bit compiler supposedly coming out,
though I haven't used it yet.  No idea if it would be the perfect solution
to your ills, or if it's buggy and would just complicate things further.
They basically scrapped the C++ Builder compiler and replaced it with a
clang-based compiler with their customizations on it.

Best regards,

James Johnston

> -----Original Message-----
> From: vtkusers-bounces at vtk.org [mailto:vtkusers-bounces at vtk.org] On
> Behalf Of matheus_viana
> Sent: Monday, November 12, 2012 19:59
> To: vtkusers at vtk.org
> Subject: Re: [vtkusers] How to overcome the memory allocation problem.
> 
> Hi Sean.
> 
> Actually there is a reason for not changing platform. I'm working with a
GUI
> that was developed in Borland C++. Unfortunately, there is not version of
> this compiler for Win64. Sad but true.
> 
> Cheers.