QGIS » QGIS Application

I can verify that it still exists in MASTER 824fd7b

I found the issue seperately when instead of calling ReadAsArray(), I called WriteArray(...) in my python plugin. Without calling WriteArray(...) no minidump is created on exit.

It happens in Windows 7, x64 running both OSGeo4W x64 MASTER and stand alone installer v. 2.12 x64 - both versions affected.

I can verify that it still exists with QGIS 2.12. My plugin crashes in exactly the same location.

This is a blocking issue for me, . . . I have been thinking that this is a gdal problem and I think most people looking at this think the same, . . . perhaps it's not. Perhaps this is a QGIS problem in the function that is called on exit. Maybe there is an exception in that function that needs to be caught. Is that a python function or is it a QGIS c++ call at that location?

I can reproduce the crash using the mentioned Python code.

Under Windows, GDAL is quite picky with its memory, because it uses its own heap. Also ownership is an issue, e.g. delete myBand; would be an error in C++. But we assume this is all properly taken care of in the python bindings.

As a workaround you can use ReadRaster() and WriteRaster(). The following code does not crash QGIS on exit under Windows:

from osgeo import gdal
inFilename = r"C:\\test.tif" 
myImg = gdal.Open(inFilename, gdal.GA_ReadOnly)
myBand = myImg.GetRasterBand(1)

scanline = myBand.ReadRaster( 0, 0, myBand.XSize, 1, myBand.XSize, 1, gdal.GDT_Byte )
import array
array_of_bytes = array.array('B', scanline)

myBand = None
myImg = None

Could you please try with the code in https://github.com/qgis/QGIS/pull/2755 ?
I cannot reproduce due to some problem with the python binding of gdal on my local system

I tried myself, this issue cannot be reproduced (for me) by using the code in https://github.com/qgis/QGIS/pull/2755

I actually cannot reproduce this with master branch either (as of b6c714ac20ea595ebf3136ae8facae0520acbe5f)
Is the .tif file to use irrelevant ? I'm using one from the testsuite:

from osgeo import gdal                                                          
inFilename = r"./output/python/plugins/processing/tests/data/raster.tif"        
myImg = gdal.Open(inFilename, gdal.GA_ReadOnly)                                 
myBand = myImg.GetRasterBand(1)                                                 
myData = myBand.ReadAsArray()                                                   
myData = None                                                                   
myBand = None                                                                   
myImg = None

I just tried with 2.12.3 and the latest nightly build (up to commit 0a64c16) with raster.tif and the issue is still present in both cases. It's a clean install on Windows 7 using OSGeo4W 64 bit installer.

I don't have the build environment set up so I haven't tested the pull request but I will try to give it a go.

Radoslaw Guzinski wrote:

I just tried with 2.12.3 and the latest nightly build (up to commit 0a64c16) with raster.tif and the issue is still present in both cases. It's a clean install on Windows 7 using OSGeo4W 64 bit installer.

I have the same result on the latest nightly build (0a64c16).

this is still an issue on the latest master (tested on windows).

Can't reproduce on latest master / Fedora.

Matthias - I've only been able to reproduce this under Windows.

see also: #14648

it affects also a few Processing tools.

Just tested with GDAL 2.2.0 on Windows: the issue is still present in 2.18.8 but I couldn't reproduce it with latest 2.99 nightly (d55fa22).

I'm also having this problem with gdal_merge.py from QGIS 2.18.11 64-bit on Win10. It's a real show-stopper for me since it's blocking my scripting.

Probably a duplicate of OSGeo4W #466

I confirm that the issue was fixed by the gdal update. Thanks Jurgen!