Bug #96610 InnoDB: Assertion failure in thread 140012361598720 in file rem0rec.cc line 578
Submitted: 22 Aug 0:49 Modified: 23 Aug 8:11
Reporter: Michael Finch Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.43 OS:CentOS (3.10.0-957.12.2.el7.x86_64)
Assigned to: Bogdan Kecman CPU Architecture:x86
Tags: multi_range_read

[22 Aug 0:49] Michael Finch
Description:
We've seen multiple MySQL crashes on this database with the following error:

2019-08-20 22:57:59 7f572b13c700  InnoDB: Assertion failure in thread 140012361598720 in file rem0rec.cc line 578
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:57:59 UTC - mysqld got signal 6 ;
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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=801
max_threads=4098
thread_count=609
connection_count=607
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4810733 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x30b5c50
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 = 7f572b13bd40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8fcb9c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x683fa1]
/lib64/libpthread.so.0(+0xf5e0)[0x7f68dbad75e0]
/lib64/libc.so.6(gsignal+0x37)[0x7f68d9be01f7]
/lib64/libc.so.6(abort+0x148)[0x7f68d9be18e8]
/usr/sbin/mysqld[0x9e17ab]
/usr/sbin/mysqld[0xa18ce1]
/usr/sbin/mysqld[0x96d499]
/usr/sbin/mysqld(_ZN7handler17ha_index_read_mapEPhPKhm16ha_rkey_function+0x118)[0x5ce698]
/usr/sbin/mysqld(_ZN7handler16read_range_firstEPK12st_key_rangeS2_bb+0x66)[0x5ceaf6]
/usr/sbin/mysqld(_ZN7handler21multi_range_read_nextEPPc+0x86)[0x5c4966]
/usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x4b)[0x80cf5b]
/usr/sbin/mysqld(_ZN26QUICK_ROR_INTERSECT_SELECT8get_nextEv+0xcc)[0x81fb9c]
/usr/sbin/mysqld(_Z8filesortP3THDP5TABLEP8FilesortbPyS5_+0x13ee)[0x7e85ce]
/usr/sbin/mysqld(_ZN13st_join_table10sort_tableEv+0x10e)[0x6e536e]
/usr/sbin/mysqld(_Z21join_init_read_recordP13st_join_table+0x29)[0x6e5589]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0xdd)[0x6e306d]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x3e8)[0x6e23f8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x275)[0x72b6d5]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x195)[0x72bf65]
/usr/sbin/mysqld[0x58863d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2c2e)[0x70684e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_stateb+0x418)[0x70aec8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xf78)[0x70c618]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a2)[0x6d9282]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6d9320]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x933c06]
/lib64/libpthread.so.0(+0x7e25)[0x7f68dbacfe25]
/lib64/libc.so.6(clone+0x6d)[0x7f68d9ca334d]

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

How to repeat:
Not sure.
[23 Aug 8:11] Bogdan Kecman
Hi,

This is a crash of a non-Oracle MySQL binary. If you cannot produce a reproducible test case that we can use to reproduce the bug on Oracle MySQL binary there's not much we can do to help.