Memory leak in document() function in xalan 2006-05-10 - By Paul Hunnisett
We are currently working with xalan 2.6. There are a lot of dependencies so
I'm not sure if upgrading to 2.7 would be easy for us.
Anyway, the problem that we're having is that one application uses an XSL
transform and relies on a helper xml file which is pulled in via the
document() function. We are finding that this causes massive memory
problems. I can only assume (perhaps I'm wrong on this) that xalan is
gettign a dom of that file for every document() call and then not releasing
references to that object. Has anyone else come across anything like this?
Does anyone have any wisdom as to how we might go about working around
this? We also run these stylesheets in MSXML which, I'm told, doesn't
supprot XSLT 2 - so any XSLT 2 solutions may not work for us...
Cheers
Paul Hunnisett
We are currently working with xalan 2.6. There are a lot of dependencies
so I'm not sure if upgrading to 2.7 would be easy for us.<br><br>Anyway, the
problem that we're having is that one application uses an XSL transform and
relies on a helper xml file which is pulled in via the document() function.
We are finding that this causes massive memory problems. I can only
assume (perhaps I'm wrong on this) that xalan is gettign a dom of that file for
every document() call and then not releasing references to that object.
Has anyone else come across anything like this?
<br><br>Does anyone have any wisdom as to how we might go about working around
this? We also run these stylesheets in MSXML which, I'm told, doesn't
supprot XSLT 2 - so any XSLT 2 solutions may not work for us...<br><br>
Cheers<br><br>Paul Hunnisett<br>
|
|
