[ http://issues.apache.org/jira/browse/XALANJ-2168?page=comments#action_12315665 ]
Brian Minchau commented on XALANJ-2168: --------------------------------------- This issue comes up mainly with SQL extensions because that is an extension that creates complex variables on the stack. The SQL extension is creating a DTM and a local variable. When the variable stack is dropped the DTM should be released. The suggested fix by Glenn is releasing the DTM in the code that is running the transformation, but John G. thinks this can be more generically handled with the variables stack, because when stack frames are returned for garbage collection that is fine, but it doesn't walk the stack frame to see if it is an XObject and call the destroy() function on it. This code may fix this problem but other objects may run into the same problem. The DTM is more complex and can't just be thrown into garbage collection, it needs to be detached from the DTM manager. Any other Xalan developers willing to work on the DTM side, to work with John who understands this from the SQL extension side? > Memory Leak using xalan with Java extension > ------------------------------------------- > > Key: XALANJ-2168 > URL: http://issues.apache.org/jira/browse/XALANJ-2168 > Project: XalanJ2 > Type: Bug > Components: Xalan-extensions-(SQL) > Versions: 2.6 > Environment: Windows XP and Unix > Reporter: Glenn Crilley > Priority: Blocker > > Performing an XSL translation using the xalan paerser with an java-based > extension causes memory leake -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
