Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

empty multilinestring causes crash #20585

Closed
qgib opened this issue Mar 19, 2015 · 5 comments
Closed

empty multilinestring causes crash #20585

qgib opened this issue Mar 19, 2015 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers

Comments

@qgib
Copy link
Contributor

qgib commented Mar 19, 2015

Author Name: David Mancini (@weifageo)
Original Redmine Issue: 12413
Affected QGIS version: 2.8.1
Redmine category:data_provider/postgis
Assignee: Jürgen Fischer


One of my GIS Technicians was having an issues with a PostGIS layer, where any time an edit was attempted QGIS 2.8.1 would experience a crash dump. We then attempted to edit the same PostGIS layer using QGIS 2.6.0 and it was able to continue editing the layer's features.

After some investigation into the table itself I found the culprit. The layer we were trying to edit contained LINESTRING and MULTILINESTRING geometries. I decided to run a query to identify the number of vertices per object using the ST_NumPoints function. At the bottom of the list I noticed a row was returned with a NULL value. After selecting the items WHERE ST_NumPoints(the_geom) IS NULL I found that there was one item. Running ST_AsText(the_geom) for this feature returned MULTILINESTRING EMPTY. After I deleted this record, I was able to edit the layer once again using QGIS 2.8.1.

I just wanted to let your team know, because this situation seemed to be handled in the previous version 2.6.0 we tested in our office. This is a minor issue which I was able to overcome by cleaning the problem record out of the PostGIS database, but I just wanted to give your team the heads up.

@qgib
Copy link
Contributor Author

qgib commented Mar 19, 2015

Author Name: Jürgen Fischer (@jef-n)


  • subject was changed from PostGIS Layer Editing Causing Crash Dump on 2.8.1 to empty multilinestring causes crash

@qgib
Copy link
Contributor Author

qgib commented Mar 22, 2015

Author Name: Giovanni Manghi (@gioman)


  • crashes_corrupts_data was changed from 0 to 1
  • fixed_version_id was changed from Version 2.8.1 to Version 2.10
  • priority_id was changed from Low to Severe/Regression

@qgib
Copy link
Contributor Author

qgib commented Mar 22, 2015

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.10 to Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Mar 22, 2015

Author Name: Jürgen Fischer (@jef-n)


not reproducable here.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented May 9, 2015

Author Name: Giovanni Manghi (@gioman)


closing for the lack of feedback, please reopen if necessary.


  • resolution was changed from to invalid
  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Crash/Data Corruption labels May 25, 2019
@qgib qgib added this to the Future Release - High Priority milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant