Opened 7 years ago

Closed 6 years ago

#130 closed defect (fixed)

Drawing GeoTiff layer will cause crash with some files

Reported by: oldbucsfan Owned by: Jeff McKenna
Priority: major Milestone: 3.2.3 release
Component: MS4W - GDAL Version: 3.2.2
Keywords: Cc: injektilo
Blocked By: Blocking:

Description

Some tiff files will not load properly and will cause the server to crash. As best as I can tell, this might be sourced to GDAL. Here are example tiff files that has this problem:

​http://geostor-imagery.geostor.org.s3.amazonaws.com/index.html?prefix=State/COSL/GLO_Mosaics

These tiff files worked fine in MS4W 3.1.4, which is the last version I used.

Change History (7)

comment:1 by oldbucsfan, 7 years ago

Also just noting that this problem still happened with utilities like shp2img and gdal_translate. Definitely seems like a GDAL issue.

comment:2 by Jeff McKenna, 7 years ago

@oldbucsfan : can you create a zip of a small mapfile with a single layer, using a problem tiff file, and provide the link to that test case here?

comment:3 by oldbucsfan, 7 years ago

Here is a link to a zipped file with a problem tiff and an associated mapfile.

​http://archeology.uark.edu/GeoTiffProblem.zip

The test case would just say "Internal Server Error". shp2img and gdal_translate both crash during the run.

Last edited 7 years ago by oldbucsfan (previous) (diff)

comment:4 by injektilo, 7 years ago

I've a question. I'm newbie in use of ms4w. Can i hope that in next realease of ms4w this bug will be fixed?

comment:5 by Jeff McKenna, 6 years ago

Cc: injektilo added

This was another difficult issue. It seems the internal geotiff and libtiff library packaged with GDAL was conflicting with the newer external geotiff and libtiff libraries used in the MS4W build. To get around this, the internal geotiff and libtiff versions are now used by GDAL inside MS4W.

Please test with a new 3.2.3-beta and report back here if successful or not: ​https://www.ms4w.com/release/experimental/ms4w_3.2.3-beta1.zip

in reply to:  5 comment:6 by oldbucsfan, 6 years ago

Replying to jmckenna:

This was another difficult issue. It seems the internal geotiff and libtiff library packaged with GDAL was conflicting with the newer external geotiff and libtiff libraries used in the MS4W build. To get around this, the internal geotiff and libtiff versions are now used by GDAL inside MS4W.

Please test with a new 3.2.3-beta and report back here if successful or not: ​https://www.ms4w.com/release/experimental/ms4w_3.2.3-beta1.zip

That seems to have fixed this issue. Thanks!!!

comment:7 by Jeff McKenna, 6 years ago

Resolution: → fixed
Status: new → closed

Today's MS4W 3.2.3 (final) release has this fix included. Thanks for reporting this issue! https://ms4w.com

Note: See TracTickets for help on using tickets.