Bug #109172 Assertion failure: row0upd.cc:2839
Submitted: 22 Nov 2022 20:29 Modified: 23 Nov 2022 16:46
Reporter: Kevin Heung Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:8.0.30 OS:Ubuntu (20.04)
Assigned to: CPU Architecture:x86 (x86_64)

[22 Nov 2022 20:29] Kevin Heung
mysql crashed with the following error. (see below)
Updated to 8.0.30 near mid Sept.  
First time seeing this issue.

2022-11-22T18:48:21.113970Z 261743 [ERROR] [MY-013183] [InnoDB] Assertion failure: row0upd.cc:2839:pcur->restore_position(BTR_MODIFY_TREE, mtr, UT_LOCATION_HERE) thread 140439969105664
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:48:21 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fbb02061800
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 = 7fbaba7864d0 thread_stack 0x100000
/var/lib/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55d73c407121]
/var/lib/mysql/bin/mysqld(print_fatal_signal(int)+0x2f3) [0x55d73b2ab013]
/var/lib/mysql/bin/mysqld(my_server_abort()+0x76) [0x55d73b2ab156]
/var/lib/mysql/bin/mysqld(my_abort()+0xe) [0x55d73c40114e]
/var/lib/mysql/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x349) [0x55d73c734ba9]
/var/lib/mysql/bin/mysqld(+0x25b22e0) [0x55d73c6a72e0]
/var/lib/mysql/bin/mysqld(+0x25b5ca6) [0x55d73c6aaca6]
/var/lib/mysql/bin/mysqld(row_upd_step(que_thr_t*)+0xbe0) [0x55d73c6ac4b0]
/var/lib/mysql/bin/mysqld(+0x257aa09) [0x55d73c66fa09]
/var/lib/mysql/bin/mysqld(row_update_for_mysql(unsigned char const*, row_prebuilt_t*)+0x43) [0x55d73c670023]
/var/lib/mysql/bin/mysqld(ha_innobase::update_row(unsigned char const*, unsigned char*)+0x1bd) [0x55d73c516eed]
/var/lib/mysql/bin/mysqld(handler::ha_update_row(unsigned char const*, unsigned char*)+0x1fb) [0x55d73b3c4fcb]
/var/lib/mysql/bin/mysqld(Sql_cmd_update::update_single_table(THD*)+0x2e15) [0x55d73b224575]
/var/lib/mysql/bin/mysqld(Sql_cmd_update::execute_inner(THD*)+0xd5) [0x55d73b224e85]
/var/lib/mysql/bin/mysqld(Sql_cmd_dml::execute(THD*)+0x186) [0x55d73b1a1f06]
/var/lib/mysql/bin/mysqld(mysql_execute_command(THD*, bool)+0xa00) [0x55d73b13e5e0]
/var/lib/mysql/bin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x434) [0x55d73b143434]
/var/lib/mysql/bin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x1d17) [0x55d73b145677]
/var/lib/mysql/bin/mysqld(do_command(THD*)+0x207) [0x55d73b146977]
/var/lib/mysql/bin/mysqld(+0x11a6ef8) [0x55d73b29bef8]
/var/lib/mysql/bin/mysqld(+0x291fa8d) [0x55d73ca14a8d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7fbdcf4e5609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7fbdcec95133]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
Unfortunately, don't have a way to repeat yet.
[22 Nov 2022 20:30] Kevin Heung
Changing severity to critical since mysql crashed.
[23 Nov 2022 13:06] MySQL Verification Team
Hi Mr. Heung,

Thank you for your bug report.

However, your bug is a duplicate bug of the following bug:


Since this is a security vulnerability bug, you can not see it. That is why we have left in the original bug, that your bug is a duplicate, so that you get a note.

[23 Nov 2022 16:46] Kevin Heung

Thanks for looking at it so quickly.


Is this fixed yet?  If yes, is it included into any of the latest (or up-and-coming) mysql version?