> I re-ran my tests with the latest CVS code from the repository. > The results > are only slightly better. There are still some very large int[] > arrays that > are eating up large portions of memory. The lastest code isn't buying us > much at this point. It seems that the GVTTreeRenderer thread is > hanging on > to all these objects. I've included the latest OptimizeIT allocation > backtrace for the int[] instances.
Can you tell us if you invoke the setDocumentState(JSVGComponent.ALWAYS_DYNAMIC) method helps you, what kind of difference you see. That will help us to quantify the memory consumption. Thierry. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
