Seg Fault while using Python3.7.0

Bug #1792586 reported by gregory on 2018-09-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxml
Undecided
Unassigned

Bug Description

When iterating over elements in a largeish xml file parsed using the objectify API, the code linked to below produces a seg fault in Python 3.7.0.
However, it runs fine using 3.6.6 and in both 3.7.0 and 3.6.6 using the lxml.etree API.

See the code at https://gitlab.com/grgvt/lxml-segfault to reproduce.

I ran the tests with tox and pytest in a Virtualenv.

Python : sys.version_info(major=3, minor=7, micro=0, releaselevel='final', serial=0)
lxml.etree : (4, 2, 5, 0)
libxml used : (2, 9, 8)
libxml compiled : (2, 9, 8)
libxslt used : (1, 1, 32)
libxslt compiled : (1, 1, 32)

scoder (scoder) wrote :

Thanks for the report and the test code. I can reproduce it in Py3.7.0 and get a crash deeply inside of CPython's memory allocator. I cannot reproduce it in the latest CPython 3.7 release branch build, so I guess it's a bug on their side that was recently fixed. Py3.7.1 is scheduled for early next week, so I'll just close this bug (not in lxml) and suggest you wait for the first 3.7 maintenance release.

Changed in lxml:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers