SegFault when opening some odt document
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxml |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On PyPy 2.6.0, using both versions 3.4.4 and trunk (3.5.0.beta1), had the following backtrace :
#0 pypy_g_from_ref (l_ref_
#1 0x00007ffff5309bd8 in pypy_g_from_ref (l_ref_
#2 0x00007ffff527d879 in PyPyWeakref_
#3 0x00007fffddbbb671 in __pyx_f_
#4 0x00007fffddbbb75e in __pyx_f_
#5 0x00007fffddbbb8e3 in __pyx_f_
#6 0x00007fffddbbba3e in __pyx_tp_
#7 0x00007ffff5fe3648 in pypy_asm_stackwalk () from /home/giovanni/
#8 0x00007ffff4afbef1 in pypy_g_
#9 0x00007ffff52b80b0 in pypy_g_
........
Full backtrace is very long, since the crash happens using the trytond[1] server, using genshi[2] and relatorio[3] to generate a document.
It is reproductible, though the python line which causes the error varies. It may be because the problem is related to garbage collection, according to frames #4/#5
It happened with several odt documents, sometimes even empty documents.
Update : Can be reproduced by just running the tests on relatorio[3]
[1] http://
[2] http://
[3] http://
Python : (major=2, minor=7, micro=9, releaselevel=
lxml.etree : (3, 5, 0, -99)
libxml used : (2, 9, 2)
libxml compiled : (2, 9, 2)
libxslt used : (1, 1, 28)
libxslt compiled : (1, 1, 28)
Linux Gaia 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Note : I am posting here because the first frames seem to indicate that the crash happens in lxml related code, but this is juste an assumption.
Closing as outdated.