Bug #112424 | Crash during background rollback if both prepare and active transaction exist | ||
---|---|---|---|
Submitted: | 22 Sep 2023 3:08 | Modified: | 25 Mar 16:56 |
Reporter: | genze wu (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S6 (Debug Builds) |
Version: | 8.0.34 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution |
[22 Sep 2023 3:08]
genze wu
[22 Sep 2023 9:20]
MySQL Verification Team
Hello genze wu, Thank you for the report and feedback. regards, Umesh
[19 Oct 2023 9:07]
genze wu
git_diff.txt is the git diff of fix patch for this bug. (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_diff.txt (text/plain), 2.50 KiB.
[25 Mar 16:56]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Server 8.0.37 and 8.4.1 releases, and here's the proposed changelog entry from the documentation team: In debug builds, there was an assertion failure in InnoDB's background when a transaction it wanted to acquire an MDL lock on was no longer active. This fix is based on a patch from Genze Wu with Alibaba, thank you for the contribution. Thank you for the bug report.