diff -r f65f740e69f9 -r 8e12a575a9b5 sysperfana/memspyext/com.nokia.s60tools.memspy.help/html/reference/isolation.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/sysperfana/memspyext/com.nokia.s60tools.memspy.help/html/reference/isolation.htm Wed Apr 21 20:01:08 2010 +0300 @@ -0,0 +1,55 @@ + + + + + Isolation and Pervasiveness + + + + +

Isolation and Pervasiveness

+ +

The Isolation and Pervasiveness views are about highlighting reference +density.

+ +

The Isolation view shades objects from cold (blue) to hot +(more red) based on how “popular” they are with other objects. The +actual incoming reference count is also displayed in the box at the start of +each object. Darkest blue objects with a red zero count indicate objects that +have no references at all within the heap itself. That does not necessarily +mean they are orphans that have been leaked; they could be referenced from the +stack or from static variables instead. However, if you do think you may have a +memory leak then these zero count objects are a good place to start looking.

+ +

+ +

The Pervasiveness view is the inverse of the Isolation +view. In Pervasiveness view, objects are shaded from cold (blue) to hot (more +red) based on how many other objects they are “interested” in. The +actual outgoing reference count is also displayed in the box at the start of +the object. The other highlighted boxes within cells are the actual locations +of the potential outgoing references Heap Analyser has identified. As pure data +datatypes with no outgoing references, descriptors are distinguished in yellow +here. If you have a memory leak, bright red objects may be worth investigating +as the potential home to an abnormally large number of references. For example, +the buffer object within a large array of pointers may be highlighted in this +view, and in some cases could be the source of a leak e.g. due to forgetting to +delete objects from the array when they’re no longer needed.

+ +

+ +
Related references
+ + + + +