Bug #115793 Mysql Server abort at fsp0fsp.cc:1894:frag_n_used > 0
Submitted: 8 Aug 2024 1:45 Modified: 8 Aug 2024 9:17
Reporter: yanwen zhang Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.0.27 OS:CentOS
Assigned to: CPU Architecture:x86

[8 Aug 2024 1:45] yanwen zhang
Description:
MySQL Server repeat exit,but after serval minutes it 

2024-08-06T18:21:30.572585+08:00 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /tmp/mysqlx.sock
2024-08-06T18:21:30.572671+08:00 0 [System] [MY-010931] [Server] /home/aaa/mysql-8.0.27/bin/mysqld: ready for connections. Version: '8.0.27'  socket: '/home/aaa/mysql-8.0.27/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2024-08-06T18:21:33.131979+08:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fsp0fsp.cc:1894:frag_n_used > 0 thread 139792473167616
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.
10:21:33 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f1dc80008c0
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 = 7f23f8b48c18 thread_stack 0x100000
/home/aaa/mysql-8.0.27/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x1f7f4ae]
/home/deploy/mysql-8.0.27/bin/mysqld(handle_fatal_signal+0x323) [0x1029073]
/lib64/libpthread.so.0(+0xf630) [0x7f2922fde630]
/lib64/libc.so.6(gsignal+0x37) [0x7f2921229387]
/lib64/libc.so.6(abort+0x148) [0x7f292122aa78]
/home/deploy/mysql-8.0.27/bin/mysqld() [0xd7f2bb]
/home/deploy/mysql-8.0.27/bin/mysqld() [0x2388c10]
/home/deploy/mysql-8.0.27/bin/mysqld() [0x2388efa]
/home/deploy/mysql-8.0.27/bin/mysqld(fseg_free_step(unsigned char*, bool, mtr_t*)+0x26e) [0x2389bde]
/home/deploy/mysql-8.0.27/bin/mysqld() [0x21f2525]
/home/deploy/mysql-8.0.27/bin/mysqld() [0x21f2cff]
/home/deploy/mysql-8.0.27/bin/mysqld(trx_purge(unsigned long, unsigned long, bool)+0x47f) [0x21f49cf]
/home/deploy/mysql-8.0.27/bin/mysqld(srv_purge_coordinator_thread()+0x575) [0x21cb105]
/home/deploy/mysql-8.0.27/bin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)()> > >::_M_run()+0xbc) [0x20f6ddc]
/home/deploy/mysql-8.0.27/bin/mysqld() [0x27615af]
/lib64/libpthread.so.0(+0x7ea5) [0x7f2922fd6ea5]
/lib64/libc.so.6(clone+0x6d) [0x7f29212f196d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2024-08-06T10:21:33.461099Z mysqld_safe Number of processes running now: 0
2024-08-06T10:21:33.466137Z mysqld_safe mysqld restarted

How to repeat:
This happens at intervals of a few days, and each occurrence repeats for a while.But we don't know how repeat it.
[8 Aug 2024 9:17] MySQL Verification Team
Hi Mr. zhang,

Thank you for your bug report.

Let us inform you that this is a forum for the reports with fully repeatable test cases. Each test case should consist of a set of SQL statements leading to the problem described.

We do not see a test case here ...

Regarding a stacktrace, we could not find an existing report that has a stacktrace like this one.

Last and most important, 8.0.27 is very old release of the version 8.0. Please, try 8.0.39.

Unsupported.