Opened 3 years ago

Closed 3 years ago

#33347 closed Bug (duplicate)

django.contrib.gis.geos.MultiPolygon segfault on arm

Reported by: Horeb Parraud Owned by: nobody
Component: GIS Version: 4.0
Severity: Normal Keywords: geos multipolygon
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Hello,

I am a python django developer and since yesterday (with the release of Django4) I try to launch my project on a mac m1

Unfortunately, python crashes systematically when I use MultiPolygons (very present in the project)

versioning:
- Python 3.9
- Django 4.0
- djangorestframework-gis 0.17
- GDAL 3.3.1
- geos 3.10
shell trace:
$/> python manage.py shell
Python 3.9.9 (main, Nov 21 2021, 03:16:13)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.30.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from django.contrib.gis.geos import MultiPolygon

In [2]: p = MultiPolygon()
[1]    58500 bus error  python manage.py shell
Python traces:
VM Region Info: 0x16d754000 is in 0x16d754000-0x16d758000;  bytes after start: 0  bytes before end: 16383
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      Stack                       16c754000-16d754000    [ 16.0M] rw-/rwx SM=PRV  thread 0
--->  STACK GUARD                 16d754000-16d758000    [   16K] ---/rwx SM=NUL  ... for thread 1
      Stack                       16d758000-16e760000    [ 16.0M] rw-/rwx SM=PRV  thread 1

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libgeos_c.1.16.0.dylib        	       0x105c1d340 GEOSGeom_createCollection_r + 88
1   libgeos_c.1.16.0.dylib        	       0x105c1d330 GEOSGeom_createCollection_r + 72
2   libffi.dylib                  	       0x1a5af0050 ffi_call_SYSV + 80
3   libffi.dylib                  	       0x1a5af89e4 ffi_call_int + 948

Change History (1)

comment:1 by Mariusz Felisiak, 3 years ago

Resolution: duplicate
Status: newclosed

Currently we cannot prove that Django is at fault. Duplicate of #32600.

Note: See TracTickets for help on using tickets.
Back to Top