On Thu, Jan 17, 2002 at 08:57:36AM -0700, Jason E. Stewart wrote: > I'm really grateful that someone is memory testing XML::Xerces, I > found and eliminated a whole bunch of issues, but you just discovered > a big one.
:-) > The problem, as you pointed out, is in the ErrorHandler code > (actually, you'd find it in any of the other *Handler's as > well). Because XML::Xerces uses Xerces-C under the hood, whenever a > handler is set, I need to allocate a C++ object to proxy for the > actual Perl handler. > > After poking around for a bit, I've discovered that I'm not proplerly > storing and releasing references to either the C++ proxy object (class > XML::Xerces::PerlErrorCallbackHandler) or the handler object (class > XML::Xerces::PerlErrorHandler). I tried some quick fixes, but no luck > I'm going to have to spend some time looking at this. OK, no problem. We have a temporary work-around involving much use of fork()... Thanks for the reply - let me know if you get anywhere with this. We are considering developing a Perl interface to Pathan, our XPath extension to Xerces-C (http://software.decisionsoft.com), so hopefully I'll have an excuse to learn SWIG properly, and I'll be able to look into some of this stuff myself. cheers, Paul -- Paul Warren, Client Services DecisionSoft Ltd. Telephone: +44-1865-203192 http://www.decisionsoft.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
