so this is the cause of the problem?
then my guess why we see this now, and not in 2.0, is the new message passing for TerminationHook