Bug #115656 InnoDB: Assertion failure in thread
Submitted: 21 Jul 4:04 Modified: 22 Jul 9:00
Reporter: chao zhao Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.44 OS:Linux
Assigned to: CPU Architecture:x86

[21 Jul 4:04] chao zhao
Description:
InnoDB: Assertion failure in thread 139664384612096 in file btr0pcur.cc line 478
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == btr_pcur_get_block(cursor)->page.id.page_no()
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:41:21 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.
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=8388608
read_buffer_size=131072
max_used_connections=91
max_threads=2048
thread_count=81
connection_count=81
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 822064 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f054c082d20
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 = 7f0626084d30 thread_stack 0x40000
mysqld(my_print_stacktrace+0x3b)[0xf11c0b]
mysqld(handle_fatal_signal+0x486)[0x79f7d6]
/lib64/libpthread.so.0(+0xf8c0)[0x7f066029d8c0]
/lib64/libc.so.6(gsignal+0x37)[0x7f065e5b0387]
/lib64/libc.so.6(abort+0x148)[0x7f065e5b1a78]
mysqld[0x76f748]
mysqld(_Z26btr_pcur_move_to_next_pageP10btr_pcur_tP5mtr_t+0x28f)[0x11118ff]
mysqld[0x76e3af]
mysqld(_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm+0xedd)[0x105c8bd]
mysqld(_ZN11ha_innobase13general_fetchEPhjj+0x1c5)[0xf52e75]
mysqld(_ZN7handler11ha_rnd_nextEPh+0xfc)[0x7f4a1c]
mysqld(_Z13rr_sequentialP11READ_RECORD+0x20)[0xc37120]
mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x147)[0xca5da7]
mysqld(_ZN4JOIN4execEv+0x267)[0xc9e9c7]
mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x17d)[0xd0fe1d]
mysqld(_Z21execute_sqlcom_selectP3THDP10TABLE_LIST+0x40b)[0xccc65b]
mysqld(_Z21mysql_execute_commandP3THDb+0x406a)[0xcd2dca]
mysqld(_Z11mysql_parseP3THDP12Parser_state+0x4ad)[0xcd580d]
mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xbe3)[0xcd6503]
mysqld(_Z10do_commandP3THD+0x19f)[0xcd803f]
mysqld(handle_connection+0x290)[0xd9be50]
mysqld(pfs_spawn_thread+0x1b4)[0x128b2c4]
/lib64/libpthread.so.0(+0x8105)[0x7f0660296105]
/lib64/libc.so.6(clone+0x6d)[0x7f065e678b2d]

How to repeat:
I don't know
[22 Jul 9:00] MySQL Verification Team
Hi Mr. zhao,

Thank you for your bug report.

However, MySQL version 5.7 is not supported for quite a long time.

If you encounter a problem with 8.0 or higher, please create a new bug report.

Unsupported.