I couldn't find a reason after looking around, likely something is triggered at some point, in certain conditions.

As a workaround, I am considering to add a hard cleanup on timer to the transactions that leave too long after lifetime, with a log message to gather some useful information for troubleshooting.

If you can still get the output for gdb script on such transactions is still useful.

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