Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.6, 10.1.0, 10.2.0, 10.3.0
Description
The test case mentioned in MDEV-16063 occasionally causes a crash in AddressSanitizer-enabled builds. I have tested and repeated this in 10.0, 10.2, and 10.3 so far.
10.0 7b9486d2eb3876d55edc05173235e6ccad2e6ae3 |
AddressSanitizer: heap-use-after-free
|
…
|
#8 0x00000000006730a8 in __asan_report_load8 ()
|
#9 0x00007fded9d437bc in lock_release (trx=<optimized out>) at /mariadb/10.0/storage/innobase/lock/lock0lock.cc:4803
|
#10 0x00007fded9d432d1 in lock_trx_release_locks (trx=0x61b00003fef8) at /mariadb/10.0/storage/innobase/lock/lock0lock.cc:7047
|
#11 0x00007fded9ebe384 in trx_commit_in_memory (trx=0x61b00003fef8, lsn=1639442) at /mariadb/10.0/storage/innobase/trx/trx0trx.cc:1182
|
#12 0x00007fded9ebf173 in trx_commit (trx=0x61b00003fef8) at /mariadb/10.0/storage/innobase/trx/trx0trx.cc:1410
|
#13 0x00007fded9eb1915 in trx_rollback_finish (trx=0x61b00003fef8) at /mariadb/10.0/storage/innobase/trx/trx0roll.cc:1339
|
This rollback is executed when a client disconnects. The index name is uidx, and that object has been freed. lock->index->table->indexes contains only one index, the clustered index. The freed index object was an uncommitted index, created by ADD UNIQUE INDEX.
Next, I will try to create a DEBUG_SYNC test case for this.
Attachments
Issue Links
- causes
-
MDEV-16376 ASAN: heap-use-after-free in gcol.innodb_virtual_debug
- Closed
- relates to
-
MDEV-16063 [Draft] ASAN use-after-poison in row_sel / row_sel_step / que_thr_step
- Closed