with 2.4.1 the segfault comes from gvBurnPoint, so that may need similar
fix than gvBurnScanline
Ari
Even Rouault kirjoitti 26.3.2019 klo 20.39:
On mardi 26 mars 2019 17:50:19 CET Ari Jolma wrote:
We're seeing transient segfaults in gvBurnScanline with a huge in-memory
raster created by rast
Thanks Even,
Ari
Even Rouault kirjoitti 26.3.2019 klo 20.39:
On mardi 26 mars 2019 17:50:19 CET Ari Jolma 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
On mardi 26 mars 2019 17:50:19 CET Ari Jolma 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
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,
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
