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

Crash after selecting rows in attribute table #16435

Closed
qgib opened this issue Apr 1, 2013 · 6 comments
Closed

Crash after selecting rows in attribute table #16435

qgib opened this issue Apr 1, 2013 · 6 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Apr 1, 2013

Author Name: Alexander Bruy (@alexbruy)
Original Redmine Issue: 7483
Affected QGIS version: master

Assignee: Matthias Kuhn


Seems caused by merging dual-view branch.

Steps to reproduce:

  1. open any vector layer
  2. open attribute table
  3. select on row, then try to select another row or select several features
  4. QGIS crashes with "Segmentation fault"

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

Author Name: Matthias Kuhn (@m-kuhn)


Sorry, I can't reproduce this here.

Can somebody else confirm?

Alex, what dataprovider are you using?

I tried postgres (with and without "select at id") and shapefile.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

Author Name: Regis Haubourg (@haubourg)


Yes confirmed here right now on windows.

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

Author Name: Alexander Bruy (@alexbruy)


Tested with shapefiles (sample dataset attached) and with postgresql/postgis (connection settings http://gis-lab.info/qa/geosample.html#PostGIS) with same result. QGIS crashes with "Segmentation fault". Here is last few strings from console output

Debug: src/core/qgsmaprenderer.cpp: 369: (render) If there is a QPaintEngine error here, it is caused by an emit call
Debug: src/core/qgsmaprenderer.cpp: 387: (render) layer admin:  minscale:0  maxscale:1e+08  scaledepvis:0  extent:75.0819396972655966,49.0830841064452983 : 89.8699798583983949,57.2502746582030966  blendmode:0
Debug: src/core/qgsmaprenderer.cpp: 478: (render) Caching enabled but layer redraw forced by extent change or empty cache
Debug: src/core/qgsmaplayer.cpp: 1246: (setCacheImage) cache Image set!
Debug: src/core/qgsvectorlayer.cpp: 982: (draw) rendering v2:
SINGLE: FILL SYMBOL (1 layers) color 225,110,231,255
Debug: src/core/qgspallabeling.cpp: 1240: (prepareLayer) PREPARE LAYER admin20130402143234605
Debug: src/providers/postgres/qgspostgresconn.cpp: 804: (openCursor) Starting read-only transaction
Debug: src/core/qgsmaplayer.cpp: 1246: (setCacheImage) cache Image set!
Warning: QPaintDevice: Cannot destroy paint device that is being painted
Segmentation fault

Can't get anything useful from gdb.
Maybe local issue. Anyone else can confirm?


  • 5486 was configured as admin.tar.bz2

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

Author Name: Matthias Kuhn (@m-kuhn)


Confirmed with the attached shapefile. Will look into this.

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

Author Name: Matthias Kuhn (@m-kuhn)


The attribute table was a bit overactive in feature selection. It called setSelectedFeatures twice subsequently. Apparently QGIS didn't like this.

#496


  • status_id was changed from Feedback to In Progress

@qgib
Copy link
Contributor Author

qgib commented Apr 2, 2013

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


Fixed in changeset "255b467b4620862d81acf49325388ca927ee1f12".


  • status_id was changed from In Progress to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption labels May 24, 2019
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 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
Projects
None yet
Development

No branches or pull requests

1 participant