id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
4724	GDAL crash in ERDAS NCSEcw4_RO.dll used through Python interface	bcarpenter	warmerdam	"Unfortunately, I don't currently have the ability to pull together a test case to accompany this ticket that would reliably demonstrate the problem. My guess is that there's a ""wild C pointer"" problem, so even the Windows error dialog that implicates the NCSEcw4_RO.dll file could be a ""red herring."" When we experience the problem, the image we are examining is a .vrt file that is based on another .vrt file based on a NITF (.ntf) file. So I don't think there's even a reason for the NCSEcw4_RO.dll file that comes from the ""ERDAS ECW/JP2 SDK"" to be in the picture.

The calls we make from the Python api are:
{{{
dataset = gdal.Open()
band = dataset.GetRasterBand()
band.SetNoDataValue()
band.GetStatistics()

and possibly band.GetHistogram(), but I don't think it gets that far.
}}}

Here are the dialogs that Windows puts up when the crash happens:
[[Image(CrashDialogs.jpg)]]
I have attached the file WER0a04.dir00.zip holding the files that the above dialog refers to.

The version we are using is from the OSGeo4W Setup program and what I recall is that it was just ""1.9.1-RC2"" at the time, but now I see that the Setup program offers ""1.9.1-RC2-2"" and ""1.9.1-RC2-1"" I believe that what we are using is what is now called the ""-1"" version. "	defect	closed	normal		default	1.9.1	normal	invalid