Re: Is this GC.log summary indicating memory leak ?

From:

Eric Sosman <esosman@ieee-dot-org.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 20 Feb 2010 16:07:11 -0500

Message-ID:

<hlpj07$q80$1@news.eternal-september.org>

On 2/20/2010 3:44 PM, Lew wrote:

Krist wrote, quoted or indirectly quoted someone who said :

I am trying to find out whether our app is experiencing memory leak by
doing verbose gc on 4 days , here is the summary : (the detail is too
long too attached)

Roedy Green wrote:

Unless there is bug in the JVM, a memory leak should be impossible, no
matter what fool thing you did in your program. You can however
packrat.

In a Java context "memory leak" refers to packratting, just as in a Java
context "reference" refers to a pointer. The terminology may be
confusingly similar to, say, C++, but one must take the definitions as
the apply to the subject.

Where did you find the official Java definition of "memory
leak?" The word "leak" does not appear in the index of the JLS
nor of the JVMS, nor (unless I've missed something, which is
possible) on any of the pages where those documents discuss
OutOfMemoryError or garbage collection. So, where is it, and
what exactly does it say a "memory leak" is?

--
Eric Sosman
esosman@ieee-dot-org.invalid