Bug #108983 Delete session timestamp assertion error
Submitted: 3 Nov 2022 11:24 Modified: 4 Nov 2022 10:12
Reporter: Pedro Ferreira Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: DML Severity:S6 (Debug Builds)
Version:8.0.31 OS:Ubuntu (22.04)
Assigned to: CPU Architecture:x86 (x86_64)
Tags: delete

[3 Nov 2022 11:24] Pedro Ferreira
Description:
The following statements:

CREATE TABLE t0 AS (SELECT 2);
CREATE INDEX i0 ON t0 ((1), (CAST(TIME '00:00:00' AS DATETIME)));
SET SESSION TIMESTAMP = 1;
DELETE FROM t0;

Trigger an assertion error at ut0dbg.cc:99

my_abort();

The compilation parameters are the same as issue 108148:

-DWITH_DEBUG=1 -DWITH_ASAN=ON -DWITH_UBSAN=ON and boost library version 1.77

How to repeat:
Run the statements above.
[3 Nov 2022 11:32] Pedro Ferreira
After performing these queries in a msql client session and a exit with CTRL+C I get these leaks:

=================================================================
==4093215==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 168 byte(s) in 1 object(s) allocated from:
    #0 0x55f9c7fd77c8 in calloc (mysql/bin/mysql+0x9247c8) (BuildId: 8ef84e399a9ef675)
    #1 0x55f9c832edff in my_raw_malloc(unsigned long, int) mysql/mysys/my_malloc.cc:196:13
    #2 0x55f9c832eb16 in my_malloc(unsigned int, unsigned long, int) mysql/mysys/my_malloc.cc:81:28
    #3 0x55f9c807d1e2 in mysql_extension_init mysql/sql-common/client.cc:3248:40
    #4 0x55f9c80bbfe7 in mysql_send_query mysql/sql-common/client.cc:7558:26
    #5 0x55f9c80bedb6 in mysql_real_query mysql/sql-common/client.cc:7689:7
    #6 0x55f9c804683f in mysql_query mysql/libmysql/libmysql.cc:655:10
    #7 0x55f9c802b8a2 in build_completion_hash(bool, bool) mysql/client/mysql.cc:2844:7
    #8 0x55f9c801f617 in com_rehash(String*, char*) mysql/client/mysql.cc:4098:3
    #9 0x55f9c8023d95 in reconnect() mysql/client/mysql.cc:3025:21
    #10 0x55f9c8023edb in mysql_real_query_for_lazy(char const*, unsigned long, bool) mysql/client/mysql.cc:3080:9
    #11 0x55f9c801d9c2 in com_go(String*, char*) mysql/client/mysql.cc:3314:11
    #12 0x55f9c8031681 in add_line(String&, char*, unsigned long, char*, bool*, bool) mysql/client/mysql.cc:2545:13
    #13 0x55f9c8019ce3 in read_and_execute(bool) mysql/client/mysql.cc:2300:9
    #14 0x55f9c80180d0 in main mysql/client/mysql.cc:1441:24
    #15 0x7f12907c6d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16

Indirect leak of 152 byte(s) in 1 object(s) allocated from:
    #0 0x55f9c7fd77c8 in calloc (mysql/bin/mysql+0x9247c8) (BuildId: 8ef84e399a9ef675)
    #1 0x55f9c832edff in my_raw_malloc(unsigned long, int) mysql/mysys/my_malloc.cc:196:13
    #2 0x55f9c832eb16 in my_malloc(unsigned int, unsigned long, int) mysql/mysys/my_malloc.cc:81:28
    #3 0x55f9c807d1f6 in mysql_extension_init mysql/sql-common/client.cc:3252:7
    #4 0x55f9c80bbfe7 in mysql_send_query mysql/sql-common/client.cc:7558:26
    #5 0x55f9c80bedb6 in mysql_real_query mysql/sql-common/client.cc:7689:7
    #6 0x55f9c804683f in mysql_query mysql/libmysql/libmysql.cc:655:10
    #7 0x55f9c802b8a2 in build_completion_hash(bool, bool) mysql/client/mysql.cc:2844:7
    #8 0x55f9c801f617 in com_rehash(String*, char*) mysql/client/mysql.cc:4098:3
    #9 0x55f9c8023d95 in reconnect() mysql/client/mysql.cc:3025:21
    #10 0x55f9c8023edb in mysql_real_query_for_lazy(char const*, unsigned long, bool) mysql/client/mysql.cc:3080:9
    #11 0x55f9c801d9c2 in com_go(String*, char*) mysql/client/mysql.cc:3314:11
    #12 0x55f9c8031681 in add_line(String&, char*, unsigned long, char*, bool*, bool) mysql/client/mysql.cc:2545:13
    #13 0x55f9c8019ce3 in read_and_execute(bool) mysql/client/mysql.cc:2300:9
    #14 0x55f9c80180d0 in main mysql/client/mysql.cc:1441:24
    #15 0x7f12907c6d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16

SUMMARY: AddressSanitizer: 320 byte(s) leaked in 2 allocation(s).

Should this be a separate bug report?
[4 Nov 2022 10:12] MySQL Verification Team
Hello Pedro Ferreira,

Thank you for the report and feedback.
Observed that 8.0.31 debug build is affected.

regards,
Umesh