#32600: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU
-------------------------------------+-------------------------------------
Reporter: Aapo Rista | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 3.2
Severity: Normal | Resolution: duplicate
Keywords: MultiPoint, | Triage Stage:
MultiLinestring, MultiPolygon, | Unreviewed
Segmentation fault, GIS, |
GeoDjango |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aapo Rista):
Ok, I found something in Console's Crash Reports (I left out a few hundred
of lines). See GEOSGeom_createCollection_r there.
Again, I think this is not GEOS/GDAL/Django **version** related issue (as
assumed in #32544), but a bug in GEOS/Python/libgeos or something.
{{{
Process: Python [86891]
Path:
/opt/homebrew/*/Python.framework/Versions/3.9/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: 3.9.2 (3.9.2)
Code Type: ARM-64 (Native)
Parent Process: bash [86834]
Responsible: Terminal [1531]
User ID: 502
Date/Time: 2021-03-27 16:48:34.731 +0200
OS Version: macOS 11.2.3 (20D91)
Report Version: 12
Anonymous UUID: 1F81D35A-CC9F-662C-B696-4BC56365499D
Sleep/Wake UUID: 24C66F23-05FD-4B16-BF9A-9BEF835E38FA
Time Awake Since Boot: 450000 seconds
Time Since Wake: 6200 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000016dda4000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [86891]
VM Regions Near 0x16dda4000:
Stack 16cda4000-16dda4000 [ 16.0M] rw-/rwx
SM=ALI thread 0
-->
Submap 180000000-190000000 [256.0M] r--/r--
SM=SHM machine-wide VM submap
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libgeos_c.1.dylib 0x000000010528873c
GEOSGeom_createCollection_r + 88
1 libgeos_c.1.dylib 0x000000010528872c
GEOSGeom_createCollection_r + 72
2 libffi.dylib 0x0000000194e64050 ffi_call_SYSV +
80
3 libffi.dylib 0x0000000194e6c9d8 ffi_call_int +
944
4 _ctypes.cpython-39-darwin.so 0x0000000103f38684
_ctypes_callproc + 856
5 _ctypes.cpython-39-darwin.so 0x0000000103f330f4 PyCFuncPtr_call
+ 220
6 org.python.python 0x00000001024cbbe0 _PyObject_Call
+ 128
7 org.python.python 0x00000001025c2030
_PyEval_EvalFrameDefault + 40440
8 org.python.python 0x00000001025b7290
_PyEval_EvalCode + 436
9 org.python.python 0x00000001024cbe7c
_PyFunction_Vectorcall + 364
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32600#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.0916f9ca9a6a1a23b265e2b976254e8f%40djangoproject.com.
