Bug #107149 mysqld got signal 11 at btr_cur_compress_if_useful

• Submitted: 28 Apr 2022 10:59
• Modified: 28 Apr 2022 14:22
• Reporter: zhijun long
• Status: Can't repeat
• Category: MySQL Server: InnoDB storage engine
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any

[28 Apr 2022 10:59] zhijun long

Description:
mysqld got signal 11 at btr_cur_compress_if_useful in line 5090. The cause is that there is a null pointer.

5062 btr_cur_compress_if_useful(
5089                 if (cursor->rtr_info->thr != NULL) {
5090                         trx = thr_get_trx(cursor->rtr_info->thr);
5091                 }

2022-04-25T17:45:15 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=579
max_threads=0
thread_count=94
connection_count=94
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 153805 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc7dfc00000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fc7e19f9590 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x3b)[0xf474bb]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x423)[0x7de503]
/lib64/libpthread.so.0(+0xf700)[0x7fcdf2d6a700]
/usr/local/mysql/bin/mysqld(_Z26btr_cur_compress_if_usefulP9btr_cur_tmP5mtr_t+0xc9)[0x1134689]
/usr/local/mysql/bin/mysqld(_Z19rtr_node_ptr_deleteP12dict_index_tP9btr_cur_tP11buf_block_tP5mtr_t+0x54)[0x1222cc4]
/usr/local/mysql/bin/mysqld(_Z24rtr_merge_and_update_mbrP9btr_cur_tS0_PmS1_PhP11buf_block_tS4_P12dict_index_tP5mtr_t+0xb2)[0x1222db2]
/usr/local/mysql/bin/mysqld(_Z12btr_compressP9btr_cur_tmP5mtr_t+0x143f)[0x1128ddf]
/usr/local/mysql/bin/mysqld(_Z26btr_cur_compress_if_usefulP9btr_cur_tmP5mtr_t+0x150)[0x1134710]
/usr/local/mysql/bin/mysqld(_Z26btr_cur_pessimistic_deleteP7dberr_tmP9btr_cur_tmbP5mtr_t+0x30f)[0x113a2cf]
/usr/local/mysql/bin/mysqld[0x10872cd]
/usr/local/mysql/bin/mysqld(_Z14row_purge_stepP9que_thr_t+0x972)[0x1089432]
/usr/local/mysql/bin/mysqld(_Z15que_run_threadsP9que_thr_t+0xa20)[0x103dd90]
/usr/local/mysql/bin/mysqld(srv_worker_thread+0x4a7)[0x10bcaf7]
/lib64/libpthread.so.0(+0x7e15)[0x7fcdf2d62e15]
/lib64/libc.so.6(clone+0x6d)[0x7fcdf181af9d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED

How to repeat:
Unfortunately, there's no way to reproduce it.

[28 Apr 2022 14:22] MySQL Verification Team

Hi Mr. long,

Thank you for your bug report.

However, we do not think that it is our bug.

If we look at the code:

 if (cursor->rtr_info->thr != NULL) {
   trx = thr_get_trx(cursor->rtr_info->thr);
}

we can notice that the field is already tested for NULL-ness. Hence, this looks like a glitch in your hardware, most likely in RAM modules, which is transient.

If you are, however, able to repeat this problem, then we need a fully repeatable test case for MySQL 8.0.29, so that we can further process your report.

Thanks in advance.