Bug #119186 after clone over,mysql crash.
Submitted: 18 Oct 2025 2:55 Modified: 18 Oct 2025 9:06
Reporter: dakun li Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Clone Plugin Severity:S1 (Critical)
Version:8.0.25 OS:Any
Assigned to: CPU Architecture:Any

[18 Oct 2025 2:55] dakun li
Description:
We used MySQL's clone feature to perform a data clone. Shortly after running, a crash occurred simultaneously on one primary and two replica servers. We suspect that this issue may be related to a bug in the clone functionality.

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.
07:08:15 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x2c3028000
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 = 7ed7b0586bc8 thread_stack 0x46000
/lingtian/opt/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x2079c3e]
/lingtian/opt/mysql/bin/mysqld(handle_fatal_signal+0x323) [0x10616b3]
/lib64/libpthread.so.0(+0xf630) [0x7f08039c1630]
/lib64/libc.so.6(gsignal+0x37) [0x7f08019d6387]
/lib64/libc.so.6(abort+0x148) [0x7f08019d7a78]
/lingtian/opt/mysql/bin/mysqld() [0xdafadb]
/lingtian/opt/mysql/bin/mysqld() [0x24aa0d3]
/lingtian/opt/mysql/bin/mysqld(fseg_free_page(unsigned char*, unsigned int, unsigned int, bool, mtr_t*)+0xf2) [0x24aa262]
/lingtian/opt/mysql/bin/mysqld(lob::first_page_t::dealloc()+0x23) [0x24fb713]
/lingtian/opt/mysql/bin/mysqld(lob::purge(lob::DeleteContext*, dict_index_t*, unsigned long, unsigned long, unsigned long, upd_field_t const*)+0x1cce) [0x250022e]
/lingtian/opt/mysql/bin/mysqld(lob::BtrContext::free_externally_stored_fields(unsigned long, unsigned long, bool, unsigned long)+0x237) [0x21bc037]
/lingtian/opt/mysql/bin/mysqld(btr_cur_pessimistic_delete(dberr_t*, unsigned long, btr_cur_t*, unsigned int, bool, unsigned long, unsigned long, unsigned long, mtr_t*, btr_pcur_t*)+0x2fa) [0x23955ca]
/lingtian/opt/mysql/bin/mysqld() [0x22b5b8f]
/lingtian/opt/mysql/bin/mysqld(row_purge_step(que_thr_t*)+0x6dd) [0x22b91dd]
/lingtian/opt/mysql/bin/mysqld(que_run_threads(que_thr_t*)+0xba8) [0x225bec8]
/lingtian/opt/mysql/bin/mysqld(srv_worker_thread()+0x3b3) [0x22ee763]
/lingtian/opt/mysql/bin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xa5) [0x21fb095]
/lingtian/opt/mysql/bin/mysqld() [0x282162f]
/lib64/libpthread.so.0(+0x7ea5) [0x7f08039b9ea5]
/lib64/libc.so.6(clone+0x6d) [0x7f0801a9eb0d]

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:
no repeat
[18 Oct 2025 9:06] MySQL Verification Team
If you can repeat this crash on versions 8.0.43, 8.4.6, or 9.4.0 or newer, please reopen this bug.