Tang, Charlie Y. wrote:
I've included an html output of JProfiler with which the program was ran
for 4 days or so.. it appears the problem lies with some of the java
primitives that batik maybe using such as char[] ?!
Hi Charlie,
Thanks for including this, however I'm a little unsure of how to read this. So the major hitters are "char[]", "byte[]", and "int[]" (int[] being the largest by far). My suspicion is that the new "char[]" are almost all string instances, and the byte[] and int[] arrays are almost all BufferedImage data.
However, what I'm unsure of is what the Difference column is telling us. So if we created 17K new strings that is only a problem if we don't drop 17K old strings. So do you know is that an "aggregate" string instance change ([EMAIL PROTECTED] - [EMAIL PROTECTED]) or is that just the number of new instances ([EMAIL PROTECTED] - #instances still live from t1)?
Also this tells me a little about what the problem might be, but really what needs to be done is to look at a sample of the new live instances and see what is keeping them live (and what is keeping them live, and what is keeping them live... until you get to something "interesting").
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
