Ticket #3513 (closed bug: fixed)

Opened 2 years ago

Last modified 2 years ago

rasters causing qgis to crash

Reported by: lutra Owned by: rblazek
Priority: critical: causes crash or data corruption Milestone: Version 1.7.0
Component: Rasters Version: Trunk
Keywords: Cc: pcav
Platform Version: Platform: Debian
Must Fix for Release: Yes Awaiting user input: no

Description

Using r15215 under Ubuntu.

I think I found some kind of raster that causes QGIS to crash when the project CRS is not equal to the raster crs.

[Note1: Yes, I know that QGIS can't reproject rasters, but I guess that this kind of crashes should be avoided.]

[Note2: I don't see the same happen with the rasters in the qgis sample data set]

Example:

*) pick the attached raster, it is a geotiff defined in epsg:3763

*) set the project CRS as wgs84, epsg:4326

*) the raster obviously disappear from the canvas.

*) try zooming to the layer and/or changing the zoom level with the mouse wheel: QGIS starts eating memory and after a few seconds it crashes. Seg Fault.

*) I found other similar rasters that cause instant crash when the project crs is set to wgs84 and the user try to zoom to the layer

If it warp the same sample raster in wgs84 and I try the other way (project in epsg:3763) qgis does not crash.

I tested also r15223 with same results.

Attachments

testpct.tif Download (90.1 KB) - added by lutra 2 years ago.
testpctwgs84.tif Download (82.2 KB) - added by lutra 2 years ago.

Change History

Changed 2 years ago by lutra

Changed 2 years ago by lutra

Changed 2 years ago by pcav

Confirmed. Syslog says:

Feb 21 17:39:40 ursus kernel: [35706.012419] qgis.bin[31635]: segfault at 7f86100cb000 ip 00007f865393e761 sp 00007ffff0f25ea8 error 6 in libc-2.11.2.so[7f86538bf000+158000]

Changed 2 years ago by aghisla

I can't reproduce the bug, with Fedora 14 up-to-date and QGIS r15378.

Any hint of different package versions between Fedora and Ubuntu?

Changed 2 years ago by lutra

  • status changed from new to closed
  • resolution set to fixed

Well... now with raster OTFR this problem is certainly fixed. At least in my Ubuntu box. Reopen if necessary.

Note: See TracTickets for help on using tickets.