Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#32927 closed Bug (duplicate)

Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with gdal 3.3.1

Reported by: szunami Owned by: nobody
Component: Database layer (models, ORM) Version: 3.2
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I am able to exactly reproduce the issue described here: https://code.djangoproject.com/ticket/32600 , however I am using gdal 3.3.1 which is the current stable version of gdal supplied via homebrew.

I'll note that gdal 3.3.1 is not officially supported (cf https://docs.djangoproject.com/en/3.2/ref/contrib/gis/install/geolibs/). However, homebrew does not make it easy to install older versions of tools.

Change History (3)

comment:1 by Mariusz Felisiak, 3 years ago

Component: UncategorizedDatabase layer (models, ORM)
Resolution: duplicate
Status: newclosed
Type: UncategorizedBug

It's a duplicate #32600 where we believe Django is not at fault.

I also added a separate ticket to confirm support for GDAL 3.3, see #32928.

comment:2 by szunami, 3 years ago

@Mariusz I can still reproduce this issue locally, after having just installed django from main. Is this expected?

python
Python 3.9.6 (default, Jun 28 2021, 19:24:41)
[Clang 12.0.5 (clang-1205.0.22.9)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import django
>>> django.get_version()
'4.0.dev20210719094220'
>>> from django.contrib.gis.geos import Polygon, MultiPolygon
>>> MultiPolygon(
...     Polygon(((-10, 10), (-10, -10), (10, -10), (10, 10), (-10, 10)))
... )
[1]    5688 segmentation fault  python3

comment:3 by Mariusz Felisiak, 3 years ago

If you have any additional details, please add a comment to the #32600, see also comments 2 and 3. Currently we cannot prove that Django is at fault.

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