hash-verifying scenario above, but generally users avoid such things; and when they don't they can expect other things to get blocked, possibly in the opposing process. Subjectively, weird blocking &ndash; caused by the other side acting pathologically &ndash; is a lot more acceptable at session-start or session-end than something like that occuring mid-session.</p>
<p >So what's the exact proposal? It's this: If A dtor begins executing, it must first block until it knows B dtor has begun executing; but onc