We have an incredibly frustrating, show-stopping problem using lxml (under
Deliverance, in front of a repoze.zope2 pipeline serving up a Plone site) on
Under high load, the Python process crashes. There is no traceback in the log,
so I can't identify where it actually happens, but we get a Windows error
dialogue saying python.exe (or pythonservice.exe if running as a Windows
service) has crashed in etree.pyd (at some binary address, no line numbers or
The Deliverance (0.3/trunk) rules use fairly complex xpath expressions. We're
trying to simplify these, but there's nothing obviously wrong, and in any case
it shouldn't crash.
We've tried to run both multi-threaded and single-threaded 'paster' processes:
the problem happens with both. I did read somewhere that it's possible to build
a single-threaded lxml egg (?), but I haven't found one.
We would be incredibly grateful for any help with (a) debugging and (b)
resolving this. At present, we're having to fight a lot of nervousness regarding
the production-worthiness of our Deliverance/lxml based solution, which is
rather unfortunate. :-(