[Django] #32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with gdal 3.3.1

54 views
Skip to first unread message

Django

unread,
Jul 14, 2021, 10:49:42 AM7/14/21
to django-...@googlegroups.com
#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-----------------------------------------+------------------------
Reporter: szunami | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/32927>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 14, 2021, 11:59:11 AM7/14/21
to django-...@googlegroups.com
#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-------------------------------------+-------------------------------------
Reporter: szunami | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => duplicate
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => Bug


Comment:

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:1>

Django

unread,
Jul 19, 2021, 9:42:26 AM7/19/21
to django-...@googlegroups.com
#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-------------------------------------+-------------------------------------
Reporter: szunami | Owner: nobody

Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by szunami):

@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
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:2>

Django

unread,
Jul 19, 2021, 2:10:51 PM7/19/21
to django-...@googlegroups.com
#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-------------------------------------+-------------------------------------
Reporter: szunami | Owner: nobody

Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak):

If you have any additional details, please add a comment to the #32600,
see also comments [https://code.djangoproject.com/ticket/32600#comment:2
2] and [https://code.djangoproject.com/ticket/32600#comment:3 3].
Currently we cannot prove that Django is at fault.

--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:3>

Reply all
Reply to author
Forward
0 new messages