[gdal-dev] Memory fragmentation and memory consumption when warping with GCPs

[Joaquim Luis]

Joaquim Luis wrote:

> After that I wrote a MEX version of gdaltransform to be able to 
> reproject points using GCPs.
> This MEX works but it revealed serious problems. At least under Matlab.
> Matlab requires not only LOTS of memory but also that the available 
> memory is continuous.
> For example, if one needs a variable of 100 Mb the system needs to have 
> a chunk of free memory
> not less than 100 Mb. Two chunks of 99 and 1 Mb are not enough as we'll 
> have an out memory error.
> 
> Now, I just realize that when I call a MEX that links against gdal.dll 
> the memory immediately becomes
> highly fragmented. As an example of my current case, I had the largest 
> chunk of free memory
> of 1070 Mb and after loading gdal.dll the largest chunk become 540 Mb

Hello,

I follow up on the memory fragmentation issue.
I found that the fragmentation is caused by the ECW driver. If compiled without
that driver, GDAL doesn't provoke any sensible fragmentation.

Joaquim Luis