On Aug 15, 2011, at 10:50 AM, David Hess wrote:

> I should note that this mis-mapping was not just in process memory. It was a
permanent change to the database and occurs each time you open it and access an
affected object.

OK.

>
> Thinking about this some more: if that object was worked with during the pack
and yet it was ghosted and was trying to reload its state - that implies that
not only commits occurred during a pack but also a cache shrink.
>
> Is it safe for a cache shrink to occur during a pack?

I haven't studied the issue, but I would guess that it is safe.

>
> We're going to work on building a test app that can recreate this problem.

If we have that, then we can solve it for sure.