ng a long tight-loop verification of its contents &ndash; verifying hashes of millions of X-pointed objects in SHM, preventing B dtor from running. Meanwhile, A in a test program had nothing more to do and ran A dtor (closed session). Suddenly, the hash-verifier code in the tight loop was hitting hash mismatches, throwing capnp exceptions in trying to traverse the message, and so on.</p>
<p >What this means, ultimately, is straightforward: A dtor must not destroy its SHM-jemalloc arena (as accessible normal