The memory-leak concept is relative. I can only show objects not released by the JVM.
I'm creating a kind of cookie for each object showing it's creating location. When the
JVM releases the object by a GC operation, I mark that location as released (Thats how
I can say where the objects were created).
Basically, if the function that is calling A() add your new String("INTERVAL") to a
Collection, it will be showed as a memory-leak by the profiler. But remember.... A
memory leak depends on the concepts of your application. (Maybe your application
should or not allocate that memory).
Clebert
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849416#3849416
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849416
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
