-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Geoprocessing tools cause libgeos to throw SIGBUS #45226
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Crash/Data Corruption
Upstream
Needs changes in an upstream library (like Qt, Proj, GDAL, ...)
Comments
I can confirm with latest GEOS master (commit libgeos/geos@6c4b36c) by lowering the default stack size to 1 MB (instead of the default 8 MB) to make it easier to see the issue ("ulimit -s 1024" before starting QGIS). But at 2 MB, this is fine. The stack trace looks like
|
rouault
added a commit
to rouault/geos
that referenced
this issue
Sep 23, 2021
Fixes qgis/QGIS#45226 While we are it, also avoid recursive formulation for queryNodePoint()
rouault
added
the
Upstream
Needs changes in an upstream library (like Qt, Proj, GDAL, ...)
label
Sep 23, 2021
Pull request submitted to GEOS per libgeos/geos#481 |
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
Upstream
Needs changes in an upstream library (like Qt, Proj, GDAL, ...)
What is the bug or the crash?
Vector geoprocessing tools, such as Union and Intersection, can't cope with certain geometries, resulting in a SIGBUS exception getting thrown by the thread running
libgeos.3.9.1.dylib
. It seems to occur with extremely detailed geometries that overlap in complicated ways: as you can see from the attached crash report, it looks like the libgeosqueryNode()
function recurses and recurses until it runs out of stack space. Also, I've been able to work around it by either cutting the geometries into small pieces and dealing with them piecemeal, or by running Simplify and then doing the geoprocessing on the resulting layer.I've enclosed a zip file containing a sample shapefile that produces this crash; I have verified that the crash occurs even in an otherwise empty project with a new profile.
Archive.zip
QGIS_2021-09-23_1735.txt
Steps to reproduce the issue
Versions
Supported QGIS version
New profile
Additional context
Some relevant sections from crash report (full crash report attached):
...snip...
The text was updated successfully, but these errors were encountered: