Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Developer Tools >> Debugging and Profiling Tool APIs

Garbage created by IterateOverReachableObjects() / IterateOverHeap()

See here: <a href="http://forum.java.sun.com/thread.jspa?threadID=747024">http://forum.java.sun.com/thread.jspa?threadID=747024</a>
[157 byte] By [lldaedaluslla] at [2007-10-2 23:03:46]
«« Set Core Prefix , can value be a variable ?
»» problem while generating stub and skeleton in ejb
# 1

The heap iteration functions don't create objects in the java heap. I assume the issue you are seeing is that some random mutator in the application allocates some objects in the window between two iterations. If that is your issue then it might be worth seeing if you can structure the agent so that it dumps the heap references in one iteration rather than requiring multiple iterations. If you pre-tag all classes then you may have sufficient context to do this in one call to IterateOverReachableObjects. There are many improvements in this area in Mustang (Java SE 6) with the new FollowReferences function.

alan.batemana at 2007-7-14 6:17:47 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...
# 2

Hi,

a little improvement I got by putting the object tagging and reference processing in one iterateOverReachableObjects. But to identify garbage there is no other way (I think) as to do a second itearation by iterateOverHeap(untagged).

But if those function do not create garbage then the issue is cleared anyway.

Thanks, Robert

lldaedaluslla at 2007-7-14 6:17:48 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...
Developer Tools
Debugging and Profiling Tool APIs

Developer Tools New Topic

Developer Tools Hot Topic

Developer Tools

All Classified