[MDEV-32345] Assertion failure in file D:\winx64-packages\build\src\storage\innobase\trx\trx0trx.cc line 1252 Created: 2023-10-03  Updated: 2023-11-06

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.6.15
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Paul Rothrock Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Windows Server 2016

Issue Links:
Duplicate
duplicates MDEV-31780 InnoDB: Assertion failure in file D:\... Closed

 Description   

Full crash dump in comment, but here are the details:

InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\trx\trx0trx.cc line 1252
InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mariadbd startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
231002 15:12:01 [ERROR] mysqld got exception 0x80000003 ;

This has so far only happened once, but this shows that their bug was not fixed by the previous ticket MDEV-31780

 Comments   
Comment by Marko Mäkelä [ 2023-10-04 ]

I think that we will need a reproducible test case or an execution trace similar to rr record and rr replay, to be able to say what leads to this failure.

Has this been confirmed to be not a duplicate of MDEV-25163? (Does this occur when the rowid filter is disabled?)

Generated at Thu Feb 08 10:30:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.