[lxml-dev] Unable to solve a crash on Windows with LXML

[Robert Liebeskind]

Hello.  We are building a product that uses Python 2.5 and LXML (2.1.4  
at present) on Windows in a highly multi-threaded environment. We have  
been trying to resolve an issue that causes Python to throw an  
unhandled exception in Windows for a few months now. We have been  
unsuccessful and we are running out of time.  The issue appears to  
involve lxml freeing the same pointer twice.  We have already compiled  
a debug build of lxml and this is what DevStudio reports when we run  
with this build.  We have been trying to get some more valuable  
information to provide to the mailing list but keep on hitting brick  
walls.  We need help.  Can anyone provide some suggestions?

Thank you,

Robert Liebeskind
Perfect World Corp.
robl at perfectworld.net

The information contained in the transmission is intended for the  
named receiver only.  The transmission may contain privileged and  
confidential material.  If you are not the named recipient, please be  
advised that any use, dissemination or unauthorized copying of the   
materials is strictly prohibited.  If you have received this  
transmission in error, please notify the offices of Perfect World  
Corporation and delete the received transmission. Thank you.