My brain interpreted it as the patch had not been applied to the trunk by a
committer (which is true), not that it never even made it to the list in
the first place.
Does the list block all attachments or just if they are a certain size.
Perhaps you could gzip or zip the patches if the latter.
In message <[EMAIL PROTECTED]>
"Doug Bryant" <[EMAIL PROTECTED]> wrote:
> Are the two patches referred to here (
> http://rubyforge.org/pipermail/libxml-devel/2007-May/thread.html ) by Jon
> Burgess* *the ones which should be applied? Looking back through the
> archive, there seems to b
Tom,
Are the two patches referred to here (
http://rubyforge.org/pipermail/libxml-devel/2007-May/thread.html ) by Jon
Burgess* *the ones which should be applied? Looking back through the
archive, there seems to be a patch you are referring, but I can't seem to
track it down.
Doug
On 6/11/07,
thanks Tom. I'll give it a shot & let you know. It is consuming all the
memory on the production box every other day. (All being all physical &
swap memory.)
Doug
On 6/11/07, Tom Hughes <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]>
Doug Bryant <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]>
Doug Bryant <[EMAIL PROTECTED]> wrote:
> What's the status on the memory leaks? They seem to be documented in the
> issue tracker and mailing list and I experience them in my application as
> well. They seem to come from when you create & merge xml nodes &
What's the status on the memory leaks? They seem to be documented in the
issue tracker and mailing list and I experience them in my application as
well. They seem to come from when you create & merge xml nodes &
documents. I'm using 0.4.0 pre1.
I unfortunately don't have the time nor the C exp
