Bug 45188

GemStone/S 64 Bit

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, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.1.6, 2.3.1, 2.3, 2.2.5.4, 2.2.5, 2.2.4, 2.2.3, 2.2

All Platforms

3.2

quickObjectAuditWithLevel: reports of objects referencing invalid oops later reported nonexistent

One of the short-cuts taken by quickObjectAuditWithlevel: that allow it to run faster than a normal objectAudit: has a side-effect that will cause objects reported as referencing invalids oops to also be reported as non-existent.  For example, you might see something like this:

--------------------
object XXXX oops[N] has value ZZZZ which is not a valid oop
...
GemStone is now beginning a detailed re-scan of the Repository to obtain specific diagnoses of the above problems.
...
Object YYYY, of class C, at 1-based offset N, references nonexistent object XXXX
----------------------

In this case, you can safely ignore the report that object XXXX is nonexistent.


Last updated: 4/17/15