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

GEOS exceptions crash QGIS on windows #22709

Closed
qgib opened this issue May 1, 2016 · 33 comments
Closed

GEOS exceptions crash QGIS on windows #22709

qgib opened this issue May 1, 2016 · 33 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Labeling Related to QGIS map labeling Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented May 1, 2016

Author Name: Anita Graser (@anitagraser)
Original Redmine Issue: 14752
Affected QGIS version: 3.0.0
Redmine category:labelling


The same project that works fine in qgis-dev and qgis-rel-dev (tested on Windows) crashes qgis 2.14.2. The dump file is attached.

It also used to crash 2.14.1 while the then qgis-rel-dev version worked. Therefore, back then, I assumed the issue had been fixed ... but it seems to be much more mysterious.



Related issue(s): #26126 (relates)
Redmine related issue(s): 18235


@qgib
Copy link
Contributor Author

qgib commented May 1, 2016

Author Name: Anita Graser (@anitagraser)


  • 9871 was configured as qgis-20160501-162647-4308-8588-f5763f0.zip

@qgib
Copy link
Contributor Author

qgib commented May 1, 2016

Author Name: Nyall Dawson (@nyalldawson)


I can't reproduce (using Linux)

@qgib
Copy link
Contributor Author

qgib commented May 1, 2016

Author Name: Anita Graser (@anitagraser)


Another user reported the issue to me, so it's not a local issue on my machine. Maybe Win-specific.

@qgib
Copy link
Contributor Author

qgib commented May 22, 2016

Author Name: Giovanni Manghi (@gioman)


This is what I see on Windows:

  • seems ok up to 2.12 (tested 2.8, 2.10 and 2.12)
  • 2.14.3, project opens, no crash, empty canvas
  • master, project opens, no crash, map cannot be zoomed or panned.

  • category_id was configured as Project Loading/Saving

@qgib
Copy link
Contributor Author

qgib commented May 22, 2016

Author Name: Giovanni Manghi (@gioman)


  • master, project opens, no crash, map cannot be zoomed or panned.

weird, tested again and is ok on master (still not ok on 2.14.3, but no crash also).

@qgib
Copy link
Contributor Author

qgib commented May 22, 2016

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented May 25, 2016

Author Name: Anita Graser (@anitagraser)


The crash seems gone in 2.14.3 (OSGeo4W version). The project even shows up correctly on canvas (not empty as Giovanni mentioned).

In master, the canvas appeared empty when I first tried opening it. Used "zoom to extent" and it displayed fine. When I closed and reopenend again, everything looked ok from the beginning.

Bit strange ... Will reopen if crashes reoccur.


  • status_id was changed from Feedback to Closed

@qgib
Copy link
Contributor Author

qgib commented Aug 1, 2016

Author Name: Anita Graser (@anitagraser)


The issue seems to have resurfaced in 2.16.1-2, causing crashes and the attached minidump (provided by K Trinko).


  • status_id was changed from Closed to Reopened
  • 10265 was configured as bugminidump.zip

@qgib
Copy link
Contributor Author

qgib commented Oct 9, 2016

Author Name: Andreas Neumann (@andreasneumann)


I can confirm the crash on loading in 2.16.3 (build #7d00cae). But the project opens fine in QGIS 2.x master (2.17, build #6e4dbc0)

However, even with 2.17, if one zooms in, rendering can be very slow. Maybe an issue with the glow/shade effects when zooming in? But that is a different issue ... Also there seem to be projection/clipping issues when zooming around ? Definitely something weird in this project.

I tested on Win 7 with the Win64 builds.

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 1

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • priority_id was changed from Severe/Regression to High

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


Update: OSGeo4W's 2.14.15 still crashes, OSGeo4W's 2.18.9 works for me but others still report issues with the stand-alone installers.


  • description was changed from The same project that works fine in qgis-dev and qgis-rel-dev (tested on Windows) crashes qgis 2.14.2. The dump file is attached.

It also used to crash 2.14.1 while the then qgis-rel-dev version worked. Therefore, back then, I assumed the issue had been fixed ... but it seems to be much more mysterious.

to The same project that works fine in qgis-dev and qgis-rel-dev (tested on Windows) crashes qgis 2.14.2. The dump file is attached.

It also used to crash 2.14.1 while the then qgis-rel-dev version worked. Therefore, back then, I assumed the issue had been fixed ... but it seems to be much more mysterious.

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


I've narrowed it down to the point city layer. When 2.14 tries to render that layer, it crashes.

There is a GEOS Exception: IllegalArgumentException: RobustDeterminant encountered non-finite numbers.


  • 11005 was configured as Screenshot 2017-05-28 21.13.34.png

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


  • 11005 removed Screenshot 2017-05-28 21.13.34.png

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


!geos_error.png!


  • 11006 was configured as geos_error.png

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


  • 11007 was configured as qgis-20170528-201313-2640-11424-a916bf4.zip

@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Anita Graser (@anitagraser)


I've further narrowed it down to activating "Discourage labels from covering features" for the city labels. If this is deactivated, the crashing stops.


  • version was changed from 2.14.2 to 2.14.15

@qgib
Copy link
Contributor Author

qgib commented May 29, 2017

Author Name: Giovanni Manghi (@gioman)


Anita Graser wrote:

I've further narrowed it down to activating "Discourage labels from covering features" for the city labels. If this is deactivated, the crashing stops.

Anita for sake of clarity would you agree if I then create a new issue ticket with just this fundamental piece of information (and the necessary dataset)?

@qgib
Copy link
Contributor Author

qgib commented May 29, 2017

Author Name: Giovanni Manghi (@gioman)


Anita Graser wrote:

I've further narrowed it down to activating "Discourage labels from covering features" for the city labels. If this is deactivated, the crashing stops.

Hi Anita,
made some test of my own.

2.14.15 crashes on project load, as well as 2.18.9.

2.18.9 nightly does not crash on project load.

BUT

I tried load the point layer in 2.18.9 nightly in a blank project, enable labels without the "Discourage labels from covering features" option and if you zoom in/out quickly with the mouse wheel is easy enough to make it crashes too...

all from osgeo4w.

@qgib
Copy link
Contributor Author

qgib commented Jun 5, 2017

Author Name: Anita Graser (@anitagraser)


Giovanni Manghi wrote:

Anita for sake of clarity would you agree if I then create a new issue ticket with just this fundamental piece of information (and the necessary dataset)?

Sure, please do.

@qgib
Copy link
Contributor Author

qgib commented Jun 5, 2017

Author Name: Giovanni Manghi (@gioman)


Anita Graser wrote:

Giovanni Manghi wrote:

Anita for sake of clarity would you agree if I then create a new issue ticket with just this fundamental piece of information (and the necessary dataset)?

Sure, please do.

this was before "I tried load the point layer in 2.18.9 nightly in a blank project, enable labels without the "Discourage labels from covering features" option and if you zoom in/out quickly with the mouse wheel is easy enough to make it crashes too..." :)

if the source of the problem was 100% that option would had made sense to create a new simpler and clearer ticket, as it does not seems the case I think that is better to keep the ticket as it is.

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2017

Author Name: Giovanni Manghi (@gioman)


Tried again on master... and here with MT enabled it seems to not crash... what about others?


  • status_id was changed from Reopened to Feedback

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2017

Author Name: Anita Graser (@anitagraser)


2.14.19 and 2.18.13 crash for me.

2.99 does not crash, but the project CRS and some layer CRS are not restored correctly :(

Seems like I don't have any version that opens the project correctly anymore.


  • version was changed from 2.14.15 to 2.18.13

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2017

Author Name: Giovanni Manghi (@gioman)


2.99 does not crash, but the project CRS and some layer CRS are not restored correctly :(

but this could be another issue. I set manually the project CRS to 3857 and it works/shows fine for me, what about there?

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2017

Author Name: Anita Graser (@anitagraser)


Yes, I can set the correct CRS manually, and so far 2.99 doesn't seem to crash ... but we've observed this behavior with previous master versions as well.

@qgib
Copy link
Contributor Author

qgib commented Nov 1, 2017

Author Name: Anita Graser (@anitagraser)


  • status_id was changed from Feedback to Open
  • subject was changed from Opening project crashes 2.14.2 but works in qgis-rel-dev to "Discourage labels from covering features" causes crashes
  • category_id was changed from Project Loading/Saving to Labelling

@qgib
Copy link
Contributor Author

qgib commented Feb 26, 2018

Author Name: Anita Graser (@anitagraser)


This issue is still live and kicking
https://gis.stackexchange.com/questions/272783/qgis-3-00-crashes-while-qgis-2-99-worked-well


  • version was changed from 2.18.13 to 3.0.0

@qgib
Copy link
Contributor Author

qgib commented Feb 26, 2018

@qgib
Copy link
Contributor Author

qgib commented Apr 19, 2018

Author Name: Nyall Dawson (@nyalldawson)


  • subject was changed from "Discourage labels from covering features" causes crashes to GEOS exceptions crash QGIS on windows

@qgib
Copy link
Contributor Author

qgib commented May 29, 2018

Author Name: Nyall Dawson (@nyalldawson)


Please test latest 3.2 master


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jun 4, 2018

Author Name: Anita Graser (@anitagraser)


Master currently doesn't crash but - considering the history of this bug - I'll only believe that it's gone when the 3.2 release opens the project without issues.

@qgib
Copy link
Contributor Author

qgib commented Jul 22, 2018

Author Name: Anita Graser (@anitagraser)


Looks like the 3.2 release is ok and does not crash. Thanks!


  • status_id was changed from Feedback to Closed
  • resolution was changed from to fixed/implemented

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 High Priority Labeling Related to QGIS map labeling Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant