After upgrade to 3.3.x (I've reproduced this bug with 3.3.0, 3.3.1 and 3.3.2), I get segmentation fault when running testsuite of Django applicition using tastypie API.
It seems to lead to deallocation of lxml objects as the backtrace ends with:
#0 subtype_dealloc (self=0x3210b00) at Objects/typeobject.c:915
#1 0x00007ffff1d9e347 in __pyx_tp_dealloc_4lxml_5etree__ElementTree (o=0x3210ea8) at src/lxml/lxml.etree.c:175081
It happens with both libxml 2.7.8 and 2.9.1.
I was able to reduce the test to parsing simple XML file using defusedxml, which is attached.
This might be security issue as well, though I'm not 100% sure.
After upgrade to 3.3.x (I've reproduced this bug with 3.3.0, 3.3.1 and 3.3.2), I get segmentation fault when running testsuite of Django applicition using tastypie API.
It seems to lead to deallocation of lxml objects as the backtrace ends with:
#0 subtype_dealloc (self=0x3210b00) at Objects/ typeobject. c:915 dealloc_ 4lxml_5etree_ _ElementTree (o=0x3210ea8) at src/lxml/ lxml.etree. c:175081
#1 0x00007ffff1d9e347 in __pyx_tp_
It happens with both libxml 2.7.8 and 2.9.1.
I was able to reduce the test to parsing simple XML file using defusedxml, which is attached.
This might be security issue as well, though I'm not 100% sure.