We run XProc scripts repeatedly within the same Java process (not headless). After a few runs of scripts that use p:xslt, a significant amount of memory remains allocated that is directly proportional to the size of the input XML source file and the number of p:xslt steps.
This did not happen with 1.0.19 and earlier.
XProc (add more p:xslt steps to amplify the problem):
Is there any feedback regarding this leak?
This is rather important for us at Oxygen, since XML Calabash runs within the Java process of our Oxygen application. This means that a memory leak stays with the application until it is restarted. After a few XProc runs that use p:xslt, the application may run out of memory due to the repeated leaks.
Top of my list, I promise. I've got some personal distractions this weekend (my mother is visiting :-) ) but I'll try to get this fixed next week. Certainly for the next release. Sorry about the delay.