Re: [FYI] heapprofile analysis

2003-03-19 Thread Stefano Mazzocchi
Gianugo Rabellino wrote: Vadim Gritsenko wrote: Holy shit! This is a *HUGE* bug. We (and Xerces) use StringBuffers all over the place!!! In fact, it seems that StringBuffer.toString() is our hotspot. I'll come up with more profile information soon. Why don't you switch to 1.3.1? Oh, sure, I

Re: [FYI] heapprofile analysis

2003-03-19 Thread Gianugo Rabellino
Vadim Gritsenko wrote: Holy shit! This is a *HUGE* bug. We (and Xerces) use StringBuffers all over the place!!! In fact, it seems that StringBuffer.toString() is our hotspot. I'll come up with more profile information soon. Why don't you switch to 1.3.1? For that matter, 1.4.0 would behave j

Re: [FYI] heapprofile analysis

2003-03-19 Thread Vadim Gritsenko
Stefano Mazzocchi wrote: Leo Sutic wrote: From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Very likely char[] or byte[]. It could be at a very low level, such as Readers and InputStreams. Could also be this: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html Bug Id472

Re: [FYI] heapprofile analysis

2003-03-19 Thread Stefano Mazzocchi
Leo Sutic wrote: From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Very likely char[] or byte[]. It could be at a very low level, such as Readers and InputStreams. Could also be this: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html Bug Id 4724129 SynopsisMem

RE: [FYI] heapprofile analysis

2003-03-19 Thread Leo Sutic
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Very likely char[] or byte[]. > It could be at a very low level, such as Readers > and InputStreams. Could also be this: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html Bug Id 4724129 SynopsisMemory leak

Re: [FYI] heapprofile analysis

2003-03-18 Thread Niclas Hedhman
On Wednesday 19 March 2003 07:10, Pier Fumagalli wrote: > On 18/3/03 23:03, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > > Pier Fumagalli wrote: > >> On 18/3/03 21:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > >>> I assume, but I'm not sure, that [xx are native internal objects, so > >>>

RE: [FYI] heapprofile analysis

2003-03-18 Thread Todd Densmore
:03 PM To: [EMAIL PROTECTED] Subject: Re: [FYI] heapprofile analysis Pier Fumagalli wrote: > On 18/3/03 21:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > > >>I assume, but I'm not sure, that [xx are native internal objects, so >>there is not much

Re: [FYI] heapprofile analysis

2003-03-18 Thread Pier Fumagalli
On 18/3/03 23:03, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > Pier Fumagalli wrote: >> On 18/3/03 21:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: >> >> >>> I assume, but I'm not sure, that [xx are native internal objects, so >>> there is not much we can do about those. Still, I would

Re: [FYI] heapprofile analysis

2003-03-18 Thread Stefano Mazzocchi
Pier Fumagalli wrote: On 18/3/03 21:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: I assume, but I'm not sure, that [xx are native internal objects, so there is not much we can do about those. Still, I would like to know what is that [10 object that accounts for so much memory. They should

Re: [FYI] heapprofile analysis

2003-03-18 Thread Pier Fumagalli
On 18/3/03 21:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > I assume, but I'm not sure, that [xx are native internal objects, so > there is not much we can do about those. Still, I would like to know > what is that [10 object that accounts for so much memory. They should be (might be) arra

[FYI] heapprofile analysis

2003-03-18 Thread Stefano Mazzocchi
Since I now finally have a *real* operating system under my fingers (one that comes with a compiler!), I'm now coming back to enjoy the freedom of native code. I found this thing called heapprofile, some 100 lines of C++ code that connect to the Java Native Profiler Interface and provide a hook