Hi,
I've built new gdal.dll (3.8.3) with ECW support. After calling function
GDALClose(dataset);
there comes to crash. I changed nothing in GDAL, or ECW code,
I only call it, from my console appication. What could be a problem with it ?
I found in google, that similar problem ws there cca 15 years
On mercredi 30 octobre 2019 00:49:24 CET TUELLER, SHAYNE R CIV USAF AFMC 519
SMXS/MXDEC wrote:
> All,
>
> We're currently using GDAL 2.3.1 on Windows to develop a shapefile editor
> for our application.
>
> We're seeing a crash in our application when we call GDALClose() on a
> dataset/layer tha
All,
We're currently using GDAL 2.3.1 on Windows to develop a shapefile editor for
our application.
We're seeing a crash in our application when we call GDALClose() on a
dataset/layer that contains a large shapefile with a large number of polygons.
We opened the shapefile and set the dataset b
Radim Blazek wrote:
Hi,
does the GDALClose function called for MEM driver call free() on the
memory passed to the driver as DATAPOINTER param? If so, how to avoid
it?
Radim,
Internally the driver tries to keep track of whether it owns the
referenced memory or not. It looks like if you use a D
Hi,
does the GDALClose function called for MEM driver call free() on the
memory passed to the driver as DATAPOINTER param? If so, how to avoid
it?
Radim
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Adeel Raza wrote:
Hi Frank,
I recently called GDALClose() on a virtual dataset (created from
GDALAutoCreateWarpedVRT()), and it was causing writing violation errors
and privileged instruction errors on the line following the GDALClose()
call. Can you shed any light on this matter? Thanks.
A
Hi Frank,
I recently called GDALClose() on a virtual dataset (created from
GDALAutoCreateWarpedVRT()), and it was causing writing violation errors
and privileged instruction errors on the line following the GDALClose()
call. Can you shed any light on this matter? Thanks.
Best Regards,
Adeel
Adeel Raza wrote:
Hi,
Should GDALClose() be called on virtual or MEM datasets?
Adeel,
Yes, it will generally result in release of associated resources.
Best regards,
--
---+--
I set the clouds in motion - turn up | Fr
Hi,
Should GDALClose() be called on virtual or MEM datasets?
Regards,
Adeel Raza.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Wendy Fay Stevenson wrote:
Hi
I'm using the GDAL api on LINUX to warp an image. I open a GIF image, warp it
and save it as a Geotiff virtual file. Then I use CreateCopy to create a GIF
file. Everything works fine except occasionally it gives a segfault when I
attempt to call GDALClose on t
Wendy,
You could try to run Valgrind on your program to get an idea of what goes
wrong. If you think that it is a GDAL bug and you have a way of reproducing
it with a small program demonstrating the problem, you could post it as a
Trac ticket.
Otherwise there is no required order for closing t
Hi
I'm using the GDAL api on LINUX to warp an image. I open a GIF image, warp it
and save it as a Geotiff virtual file. Then I use CreateCopy to create a GIF
file. Everything works fine except occasionally it gives a segfault when I
attempt to call GDALClose on the original dataset (opened w
12 matches
Mail list logo
