Actually, this seg fault occurs during normal running, not just when Ruby is exiting. We had a ton of crashing due to this. The order in which things are marked has nothing to do with the order in which things are freed, do enough work with different documents over many requests and we always eventually hit a segfault. I added some ref counting and we've been running for a while now with zero segfaults. Attached is a patch with what I did, the downside of which is that I disabled all the xpointer stuff which we don't use and I didn't have time/was unmotivated to fix. If you don't use xpointer this patch should solve your problems.
-Tom -----Original Message----- From: [EMAIL PROTECTED] on behalf of Charlie Savage Sent: Tue 9/9/2008 9:29 AM To: libxml-devel@rubyforge.org Subject: Re: [libxml-devel] Segmentation fault in document.rb >> In my view its a bug in Ruby's GC. See the emails I posted to >> ruby-core a couple month ago. There is a way to work around it, but >> haven't go to that yet. > Could you expand on it, workaround that is? Perhaps I could help you > with it. http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-core/17706?17500-18182+split-mode-vertical http://rubyforge.org/pipermail/libxml-devel/2008-July/001034.html > Does this bug persist in Ruby 1.9? I'm not sure, haven't checked. Charlie -- Charlie Savage http://cfis.savagexi.com
<<winmail.dat>>
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
