Aha.  Thank you.  My understanding (gathered from the early parts of this thread, actually) was that a reference can become fort of "orphaned" if it's embedded in a container (perhaps a list two-deep) and the original object, source of the reference, is deleted while the reference in the container continues to exist.  I had understood that under such circumstances, Python will get a bit confused when it goes to count down the references and can't find the original for the list reference.  I may have completely misunderstood the process, as I have found it rather confusing, in spite of having run all the tests early on with reference counting and garbage collecting, to try to get the hang of it.  If it doesn't necessarily happen that way, I can feel a bit better about the universe actually making more sense to me.  LOL

I don't think the problem can be related to morph creation - otherwise I'd see it cropping up more broadly.  This occurs when I loop on the multiple actorsin the comparison cycle.  It was happening before the .pyd was introduced; it was happening with the earlier .pyd version, prior to the Mesh approach; and it looks like the same thing is still happening now - whatever that thing may be.  Hmm.

I'll try the process you outline above, to do some more controlled testing.  :D  Chances are, this is another goofy Cage false alarm which can be explained by kludge-worthy coding on my part....

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.