Catch geos exception in main event loop #4309
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If something fails to catch a geos exception, at least there will be more information in the message box.
I hope to get more information next time I run into this reshape tool shows "Unknown Exception" message possibly related to CRS and snapping but not sure and cannot reproduce error.
I am not sure what exactly the reason was for GEOSException implementing a static
lastMsg
variable. It looks like this is only assigned but never used and is some really old code.