[news.eclipse.tools.hyades] Re: Number of Collected items are 0

[curtispd@xxxxxxxxxx (Curtis d\'Entremont)]

Actually, that would be very helpful. It's possible this was already fixed 
in Hyades or the Sun JVM, depending on where the problem is. I would 
recommend moving up to Hyades 3.2 - the release hasn't been posted to 
eclipse.org yet, but it should be soon.

If this doesn't fix the problem, you can report this directly as a bug on 
the eclipse.org bugzilla system.

Also, I think you're right about the fact that this isn't actually a 
command, bug more of a suggestion to the JVM. Here's what the Javadocs say 
about the System.gc() method:

"Calling this method suggests that the Java virtual machine expend effort 
toward recycling unused objects in order to make the memory they currently 
occupy available for quick reuse."

Thanks,
Curt

LO wrote:

> Hi,

> Hyades 3.0.0

> I'm running the RAC server on Solaris 8
> Eclipse IDE is running on Windows 2000
> Both are using Sun JDK 1.4.2_03

> Perhaps I should upgrade to a newer Hyades (Both Eclipse plug-in and RAC
> server) before you start performing some more investigations?
> (or switch to the newer 1.4.2_06 JVM)

> I'm note sure what to expect when I press the run GC button (long time since
> I looked into the JVMPI specs) but will the JVM actaully perform
> the GC or will it simply take it to consideration.


> BR

> Lars





> "Curtis d'Entremont" <curtispd@xxxxxxxxxx> wrote in message
> news:cq57i3$jj8$1@xxxxxxxxxxxxxxxxxx
> > Hi Lars,
> >
> > Hmm.. I'm not sure why this would be happening. It sounds like a bug on
> > the data collection side. Which platform and version of Hyades are you
> > using? I'll see if I can reproduce it...
> >
> > Thanks,
> > Curt
> >
> > Lars wrote:
> >
> > > Hi,
> >
> > > I have been using Hyades for Java profiling. But I think there is some
> > > random behaviour when
> > > using the memory leak analysis. Sometimes the 'collected items' fields
> (e.g.
> > > the number of objects
> > > that have been GC:d) are updated and sometime (most of the time) the
> field
> > > remains 0. Active instances fields are however
> > > always updated. Forcing a GC from Eclpse does not have any effect.
> >
> > > The obvious reason would be if the JVM that I'm profiling have not run
> GC or
> > > that there is a serious memory leak in my
> > > application. But I have run the JVM with GC trace enabled and GC kicks
> in
> > > every now and then. And since the fields are 0
> > > for all objects I think that Eclipse has not recieved any collected
> > > information.
> >
> > > Perhaps there is some issue with the different generations (new etc) in
> the
> > > JVM that prevents GC from collecting my objects or is there
> somethingelse
> > > that controls this behaviour.
> >
> > > Any help appreciated
> >
> > > Lars