Bug #117777 mysql crash Assertion failure: rec.cc:384
Submitted: 24 Mar 9:15 Modified: 26 Mar 5:03
Reporter: richie qain Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:8.0.31 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any

[24 Mar 9:15] richie qain 
Description:
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html","'2025-03-20T11:34:01.396231Z"
	libc.so.6(__clone+0x3f) [0x78a87fe1d05f]","'2025-03-20T11:34:01.396120Z"
	libpthread.so.0(+0xb7db) [0x78a87fee37db]","'2025-03-20T11:34:01.396019Z"
	mysqld(+0x758fca3) [0x57e5f978fca3]","'2025-03-20T11:34:01.395920Z"
	mysqld(+0x5282f90) [0x57e5f7482f90]","'2025-03-20T11:34:01.395818Z"
	mysqld(_Z10do_commandP3THD+0x5ac) [0x57e5f7e84aac]","'2025-03-20T11:34:01.395704Z"
	mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x308f) [0x57e5f7e8292f]","'2025-03-20T11:34:01.395613Z"
	mysqld(_Z20dispatch_sql_commandP3THDP12Parser_state+0xb11) [0x57e5f7e86011]","'2025-03-20T11:34:01.395467Z"
	mysqld(_Z21mysql_execute_commandP3THDb+0x1b7f) [0x57e5f7e89dbf]","'2025-03-20T11:34:01.395169Z"
	mysqld(_ZN11Sql_cmd_dml7executeEP3THD+0x2d6) [0x57e5f7f019b6]","'2025-03-20T11:34:01.395100Z"
	mysqld(_ZN11Sql_cmd_dml13execute_innerEP3THD+0xb0) [0x57e5f7f02630]","'2025-03-20T11:34:01.395016Z"
	mysqld(_ZN16Query_expression20ExecuteIteratorQueryEP3THD+0x422) [0x57e5f7f9fba2]","'2025-03-20T11:34:01.394938Z"
	mysqld(_ZN14FilterIterator4ReadEv+0x6a) [0x57e5f7b7908a]","'2025-03-20T11:34:01.394835Z"
	mysqld(_ZN22IndexRangeScanIterator4ReadEv+0x64) [0x57e5f7ce52c4]","'2025-03-20T11:34:01.394754Z"
	mysqld(_ZN7handler21multi_range_read_nextEPPc+0x60) [0x57e5f79d54c0]","'2025-03-20T11:34:01.394690Z"
	mysqld(_ZN11ha_innobase15read_range_nextEv+0x38) [0x57e5f803dcb8]","'2025-03-20T11:34:01.394620Z"
	mysqld(_ZN7handler18ha_index_next_sameEPhPKhj+0x1d4) [0x57e5f79cd954]","'2025-03-20T11:34:01.394526Z"	mysqld(_ZN11ha_innobase13general_fetchEPhjj+0x70) [0x57e5f803d3f0]","'2025-03-20T11:34:01.394457Z"
	mysqld(_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm+0x3461) [0x57e5f8419161]","'2025-03-20T11:34:01.394392Z"
	mysqld(_ZN31Row_sel_get_clust_rec_for_mysqlclEP14row_prebuilt_tP12dict_index_tPKhP9que_thr_tPS5_PPmPP16mem_block_info_tPPK8dtuple_tP5mtr_tPN3lob11undo_vers_tE+0xc2) [0x57e5f8413222]","'2025-03-20T11:34:01.394336Z"
	mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x31ba) [0x57e5f816c83a]","'2025-03-20T11:34:01.394231Z"
	mysqld(_Z24btr_search_guess_on_hashP12dict_index_tP12btr_search_tPK8dtuple_tmmP9btr_cur_tmP5mtr_t+0x7c1) [0x57e5f80ef021]","'2025-03-20T11:34:01.394159Z"
	mysqld(_Z15rec_get_offsetsPKhPK12dict_index_tPmmN2ut8LocationEPP16mem_block_info_t+0x230) [0x57e5f84b51f0]","'2025-03-20T11:34:01.394056Z"
    mysqld(_Z23ut_dbg_assertion_failedPKcS0_m+0x176) [0x57e5f84a8936]","'2025-03-20T11:34:01.393925Z"
	mysqld(_Z8my_abortv+0xa) [0x57e5f9f2d4ca]","'2025-03-20T11:34:01.393719Z"
	[0x503f322241b4]","'2025-03-20T11:34:01.393558Z"
	mysqld(_Z18print_fatal_signali+0x4e2) [0x57e5f752dce2]","'2025-03-20T11:34:01.393243Z"
New value of fp=0 failed sanity check, terminating stack trace!","'2025-03-20T11:34:01.348689Z"
Stack range sanity check OK, backtrace follows:","'2025-03-20T11:34:01.341230Z"
Cannot determine thread, fp=789f65560390, backtrace may not be correct.","'2025-03-20T11:34:01.341135Z"
terribly wrong...,"'2025-03-20T11:34:01.341038Z"
where mysqld died. If you see no messages after this, something went","'2025-03-20T11:34:01.340919Z"
Attempting backtrace. You can use the following information to find out,"'2025-03-20T11:34:01.340770Z"
Thread pointer: 0x503f3e5d5500,"'2025-03-20T11:34:01.340657Z"
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.","'2025-03-20T11:34:01.340542Z"
2025-03-20T11:34:01Z UTC - mysqld got signal 6 ;","'2025-03-20T11:34:01.340357Z"
InnoDB: about forcing recovery.,"'2025-03-20T11:34:01.339397Z"
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html","'2025-03-20T11:34:01.339301Z"
InnoDB: corruption in the InnoDB tablespace. Please refer to,"'2025-03-20T11:34:01.339194Z"
InnoDB: immediately after the mysqld startup, there may be","'2025-03-20T11:34:01.339047Z"
InnoDB: If you get repeated assertion failures or crashes, even","'2025-03-20T11:34:01.338786Z"
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.,"'2025-03-20T11:34:01.338668Z"
InnoDB: We intentionally generate a memory trap.,"'2025-03-20T11:34:01.338538Z"
2025-03-20T11:34:01.331171Z 38943217 [ERROR] [MY-013183] [InnoDB] Assertion failure: rec.cc:384 thread 132625995298560","'2025-03-20T11:34:01.338233Z"

How to repeat:
How to Repeat (Steps to Reproduce)
Unfortunately, I am unable to reproduce this issue consistently. However, it occurred under the following conditions:

Storage Engine: InnoDB
[24 Mar 12:29] MySQL Verification Team 
Hi,

Looks like you submitted the request before you finished the condition under which you reproduced the issue. Can you please share this data.

Thanks
[24 Mar 12:33] richie qain 
The issue could not be reproduced. I noticed that the adaptive hash index was being used, so I disabled it
[26 Mar 5:03] MySQL Verification Team 
Hi,

I cannot reproduce the problem and since you are using a version of MySQL server that is rather old I can suggest you upgrade and reopen the report if you happen to reproduce it with latest MySQL server.

Thank you for using MySQL