Bug 41764

Informational

GemStone/S 64 Bit

3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.4.4, 2.4.4.3, 2.4.4.2, 2.4.4.1, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.1.7, 2.3.1.6, 2.3.1.5, 2.3.1.4, 2.3.1.3, 2.3.1.2, 2.3.1.1, 2.3.1, 2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.4, 2.2.x, 2.2, 2.1.5, 2.1.4, 2.1.x, 2.0.x, 1.2.6, 1.2.5, 1.x

all

findReferencePathToObject: not intended for use with Classes/Metaclasses

The method Repository >> findReferencePathToObject: can be used to find references to objects in the repository, to determine why these instance are not garbage collected.  Due to the design of the code, this method does not work to find references to instances of Class or MetaClass.

Workaround

To find immediate references to instances of Class or MetaClass, use listReferences:. If this is not enough information, you can use findReferencePathToObject: to find a reference path each of the objects returned by listReferences:.


Last updated: 8/4/11