[gdal-dev] Segfault in gdalrasterize

[Sean Gillies]

Hi Ari,

The Linux rasterio wheels I've been putting on PyPI include libraries built
for compatibility with old versions of Linux, as old as CentOS 5. If there
are any differences between the OS in your cloud and what you have on your
local machines, you may experience some differences. If you can, it could
be worth building Rasterio from source for your deployments, which would
mean installing the build prerequisites (Numpy, Cython, GDAL) and running
`pip install --no-binary rasterio rasterio`.

I wonder if you're more memory contrained in the cloud than you are on your
own computer and if this is part of the trouble.

On Tue, Mar 26, 2019 at 9:50 AM Ari Jolma <ari.jolma at gmail.com> wrote:

> We're seeing transient segfaults in gvBurnScanline with a huge in-memory
> raster created by rasterio.
>
> The raster size is (67264, 51776).
>
> The segfaults happen in cloud servers, not in laptops or local virtual
> machines.
>
> Debugging is hard because rasterio installs its own libgdal but with gdb
> I see with bt
>
> #0  __memset_avx2_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:245
> #1  0x00007ffff127646f in gvBurnScanline(void*, int, int, int, double) ()
>     from ../rasterio/.libs/libgdal-c9384152.so.20.5.0
>
> Any ideas?
>
> Thanks,
>
> Ari
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev



-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20190326/46f069d7/attachment-0001.html>