Opened 13 years ago
Last modified 13 years ago
#3607 new bug
GDALTools: Inconsistent behaviour on windows standalone in QGIS 1.6
| Reported by: | custard | Owned by: | brushtyler |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
| Component: | GDALTools | Version: | 1.6.0 |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | Windows |
| Platform Version: | Awaiting user input: | no |
Description
(Paolo asked me to add my bits to the the ticket, but I can't find it so I'm making this one up. If it does exist, apologies for making more work, but can someone merge them?)
Paolo notes: In some (but not all) Windows machines (both seven and xp) we are getting crashes in gdaltools (contour, buildvrt, possibly others) [qgis 1.6, standalone]. I noticed that there are 2 gdal app folders (16 and 17). Anyone can confirm the problem? Any idea of what we can test?
I tested this on two windows machines using standalone 1.6. Both indicate that they are using QGIS 1.6.0 - "Code revision exported", and GDAL/OGR 1.5.4.
One machine is XP (32-bit), the other 7 (64-bit).
For both computers I loaded the same georeferenced jpeg (MGA94,zone 51), and used the GDALTools Contouring option. To make the processing of this file faster I set the contouring to 100 (default 10).
On the winXP 32bit machine it completed with out problems. On the win7 64bit machine, it displayed "The process crashed sometime after starting successfully" after creating the shape files but before asking what CRS to use.
The created shape files from the two machies are however, identical. (I can add them to the report if helpful)
Change History (5)
follow-up: 2 comment:1 by , 13 years ago
comment:2 by , 13 years ago
Yes. Seems to work for osgeo both 1.6 and 1.7.
The problem was with the standalone install.
The standalone version is important.
If you need to explain to a windows user how to install QGIS, or uninstall/reinstall, the standalone version makes life simpler. Being the familiar install path, it removes a hurdle to getting someone into GIS.
comment:3 by , 13 years ago
Seems to work for osgeo both 1.6 and 1.7
Ah, OK. We had what seemed to be the same problem with the osgeo 1.5 and 1.6, but I guess it could have been a different problem.
comment:4 by , 13 years ago
I wouldn't rule that out.
I've only got a small set of computers to compare with (see above), and all but mine are standalone, so I have single sample point to say it works.
Did you or Paolo (if he has had time) see any sort of patterns?
Does this occur with the osgeo nightly builds? We had the same problem previously, but not now that we are running nightly builds.