Charlie Savage wrote:
The comment says the functions were added to libxml in 2.6.27 but the
code is included for all versions <= 2.6.27 so if you happen to have
exactly 2.6.27 on your system then you get a double definition.
Yup, should be < not <=. I take it you are using 2.6.27?
Well on
There is some code in ext/libxml/ruby_xml_html_parser_context.c that
defines a couple of functions for older versions of libxml that are
included in newer versions.
Right, those were added for OS X compatibility, since it has version
2.6.16. They actually exist in older libxml versions, but a
There is some code in ext/libxml/ruby_xml_html_parser_context.c that
defines a couple of functions for older versions of libxml that are
included in newer versions.
The comment says the functions were added to libxml in 2.6.27 but the
code is included for all versions <= 2.6.27 so if you happe
What a shame. I think we should investigate alternatives, but high
memory usage is better than crashing. :'(
My thinking on this is go back through all the mark and free functions
and see which other ones theoretically could have the problem. Then
having done that review, give it anothe
What a shame. I think we should investigate alternatives, but high
memory usage is better than crashing. :'(
I should point out that we also have high load but we haven't
experienced any segfaulting - so it may be configuration dependent, but
not necessarily
I'll try and take a look at
Well, that didn't last quite as long as I had hoped.
A new version of libxml-ruby, version 1.1.0, is now available. It
includes two changes:
* Fix bug caused by the mark function being called on partially
initialized attributes.
* Revert back to libxml2's internal memory manager.
These c
#0 rxml_attr_mark (xattr=0x0) at ruby_xml_attr.c:41
#1 0xb7ed6a15 in gc_mark_children (ptr=3050895040, lev=1) at gc.c:945
#2 0xb7ed6c49 in mark_locations_array (x=0xbfc32f90, n=39) at gc.c:629
#3 0xb7ed6e17 in garbage_collect () at gc.c:1366
#4 0xb7ed79c5 in ruby_xmalloc (size=48) at gc.c:103
Charlie Savage wrote:
As you can see it is being asked to mark an attribute, but the
attribute pointer it is given is null.
Yeah, this should be easy to track down. Is it 1.9.1 by chance? Do you
have a test case?
No, it's 1.8.6 actually. I don't have a simple test case I'm afraid - it
wa
Hi Tom,
Having upgraded to libxml-ruby 1.0.0 yesterday I am now seeing
repeatable crashes in the garbage collection. The end of the trace looks
like:
#0 rxml_attr_mark (xattr=0x0) at ruby_xml_attr.c:41
#1 0xb7ed6a15 in gc_mark_children (ptr=3050895040, lev=1) at gc.c:945
#2 0xb7ed6c49 in m
Tom Hughes wrote:
Having upgraded to libxml-ruby 1.0.0 yesterday I am now seeing
repeatable crashes in the garbage collection. The end of the trace looks
like:
#0 rxml_attr_mark (xattr=0x0) at ruby_xml_attr.c:41
#1 0xb7ed6a15 in gc_mark_children (ptr=3050895040, lev=1) at gc.c:945
#2 0xb7e
Having upgraded to libxml-ruby 1.0.0 yesterday I am now seeing
repeatable crashes in the garbage collection. The end of the trace looks
like:
#0 rxml_attr_mark (xattr=0x0) at ruby_xml_attr.c:41
#1 0xb7ed6a15 in gc_mark_children (ptr=3050895040, lev=1) at gc.c:945
#2 0xb7ed6c49 in mark_locati
11 matches
Mail list logo
