DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44358>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44358 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-14 15:12 ------- Small update: I've been browsing around, and may have found the possible cause of the arrays not being collected. Theoretically, it is possible that an implementation of a tracing GC algorithm would still view the arrays as reachable if their first element is still strongly reachable... Since this is the default absolute-position property, and it is possibly referenced by a significant amount of FObjs. Maybe you could try something like: * add an empty protected cleanup() method to org.apache.fop.fo.PropertyList * add an override for this method to StaticPropertyList, and explicitly null out the first element of the member arrays * in FOTreeBuilder.MainFOHandler.endElement(), inside the if-block right after currentFObj.endOfNode(), add currentPropertyList.cleanup() as a first line -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
