[gdal-dev] gdalwarp crash

[Simon Lyngby Kokkendorff]

Hi Even,


> When you say "crashed", you mean it exited with the integer overflow error
> (to
> be opposed as the windows that is displayed by Windows when a process
> really
> crashes) ?
>

  Yes, it didn't really crash, but exited with the integer overflow error
message.

The issue is rather with the -wm 3072. The warping algorithm will currently
> cast a integer overflow error when a memory allocation above 2 GB is
> attempted.
> So you should try -wm 2047 or less. There's rarely a significant advantage
> in
> using so big values for -wm.
>

Ahh, I see. I was using win64 and just assumed that setting -vm high might
speed things up. Will try to create a tiled output image :-)
By the way, I also tried using -multi to speed up (with otherwise the same
options, I think), but got an error saying something like "Unable to aquire
IOMutex" (unfortunately I haven't got the exact output).

Thanks,
Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20130225/dcd0b8a2/attachment-0001.html>