Bug report #13374
Crash on loading MySQL geometry Layer
|Affected QGIS version:||2.10.1||Regression?:||No|
|Operating System:||Debian/Ubuntu||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||Yes||Copied to github as #:||21426|
While trying to connect to a MySQLDB serving geometries, QGIS crashes when loading the layer (POINT with only one entry).
Using 2.8.3 on Debian it crashes immediately when connecting even before it presents the list of available tables in the DB.
Using QGIS 2.10 on Ubuntu QGIS crashes when trying to load the layer. It successfully gets and presents the list of available Layers but when trying to load the POINT layer it crashes immediately after noticing that it could not get the layers SRS and therfore assuming WGS8 (which is correct in my testcase).
Crashes always generates a segfault-error without further information.
This bug does not seem to be necessarily an OGR issue, because using ogr2ogr on the machines succesfully imports a shp into MySQL and even successfully exports it from the DB back to a Shapefile without problems.
#3 Updated by Marco Lechner about 7 years ago
- Affected QGIS version changed from 2.8.3 to 2.10.1
- File QGIS_crashlog_2.10.txt added
with definitely unticked parallel rendering the error is the same (crashdump.log from available QGIS 2.10) attached. Anyway, I'm quite sure the parallel rendering was unticked when the first dump has been created as well.
#8 Updated by Marco Lechner about 7 years ago
- Status changed from Feedback to Closed
seems to be fixed using GDAL 1.11.x as described in duplicate issue.
Tested to use a mysql-Connection using QGIS 2.12.x on Ubuntu 15.04/GDAL 1.11.2 and some openSuSE using a QGIS compiled against a GDAL 1.11.x
Anyway closing this ticket, even backporting a "fix" to QGIS LTR (2.8.x) means providing a QGIS 2.8.x-Version depending on an increased GDAL-Version.