[Glass] index defined on RcIdentityBag's contains foreign object

[Dale Henrichs via Glass]

Hey Johan,

Well, Bill has checked around and this kind of thing does not look like 
anything we've seen before.

We're curious what kind of object was causing the problem.

Since you've worked around the problem, I think that we are still 
interested in taking a shot at trying to figure out what might have 
happened. If you have the tranlogs for that stone (and the inclination) 
you could ship the tranlogs to us, tell us the oop of the collection and 
the slot that you patched (and ideally the oop of the bad boy object) 
and we might be able to learn something about what happened by analyzing 
the tranlogs ... of course, we don't know how long that object has been 
there and unless the oop shows up in some recognizable pattern of 
commits we might not be able to learn anything at all. So if you have 
the time (and inclination) to package up the tranlogs, we can take a shot...

Dale

On 01/09/2015 03:54 AM, Johan Brichau via Glass wrote:
> Hi,
>
> I hit a rather strange problem while searching for a reference path to an object.
>
> An RcEqualityIndex defined on an RcIdentityBag is holding onto an instance that should not be there. It seems it is part of the array of its internal components…
> When I try to remove the index or invoke #cleanupBag, an error is thrown: #isEmpty is not understood by that instance (obviously, the code of those methods is iterating over the internal bags, sending #isEmpty …).
>
> What can I do to clean this situation?  (this is GS 2.4.4.1)
> The RcIdentityBag itself appears to be functioning properly (for now).
>
> thanks
> Johan
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass