I ran this test with the March 11th 1.5 Beta. The memory issue was not as pronounced as in the 1.1.1 release but still very evident as you can see by the numbers below. Our corporate firewall won't let me use CVS on the internet, and my home ISP was down all last night and this morning so I am currently unable to get the latest CVS build unless there is a place to download the latest snapshot (i.e like the Cocoon-Dev guys do). If you can get me the latest build, I'll try it and report my results.
-Aaron >> We are displaying an image in our Java applet using SVG and the Batik API. >> For images with larger SVG Documents we are running out of memory. For >> smaller images, we see a definate memory leak. We are displaying our SVG >> Document in a new frame. We place some action listeners on the JSVGCanvas >> to show status of the document load. Using OptimizeIT 4.0 I am >> able to see >> the memory offenders are int[] with 5108 instances and 35643K of >> memory, and >> org.apache.batik.css.CSSOMReadOnlyStyleDeclaration$AuthorValueEntry with >> 74140 instances and 2606K of memory. >> >> Any tips on helping me resolve this issue? If requested I can forward our >> Java Code that Creates a JSVGCanvas and sets the SVGDocument. > >Can you try with the current cvs code base and tell us if there is some >progress. > >Thierry. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
