Segmentation fault after upgrade to 3.3.x
Bug #1287118 reported by
Michal Čihař
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxml |
Fix Released
|
Critical
|
scoder |
Bug Description
After upgrade to 3.3.x (I've reproduced this bug with 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/
#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.
Actually defusedxml is not important, I've reduced the testcase to use lxml only, attached.