You're right, tmx too could be affected by the same issue.
In my case the memory allocated for the transaction and the uas request was the same as for a recently closed transaction. And adding the check for the message id did not completely solve the issue, because of the its per-process nature I was still facing false negative in some cases.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.