Bug #117418 MYSQL stopped running
Submitted: 9 Feb 22:22 Modified: 10 Feb 12:05
Reporter: BITS INV Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.40 OS:Any
Assigned to: CPU Architecture:Any

[9 Feb 22:22] BITS INV
Description:
2025-02-06T11:15:05.008442Z 669047 [ERROR] [MY-013190] [InnoDB] [FATAL] Some (-895701161) threads are still activeUnable to allocate memory of size 30736.
2025-02-06T11:15:05.009535Z 669047 [ERROR] [MY-013183] [InnoDB] Assertion failure: memory.cc:306:ib::fatal triggered thread 3804
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.
2025-02-06T11:15:05Z UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x25bd1e7bdd0
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...
7ff6ca062598    
7ff6ca9caf54    
7ff6cb141b50    
8059ffa8c8    
8059ffacc0    
8059ffad60    

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (25bbe4a2830): SELECT option_name, option_value FROM nd_options WHERE autoload IN ( 'yes', 'on', 'auto-on', 'auto' )
Connection ID (thread ID): 669047
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.
2025-02-06T21:51:10.814861Z 0 [Warning] [MY-011068] [Server] The syntax 'sync_master_info' is deprecated and will be removed in a future release. Please use sync_source_info instead.
2025-02-06T21:51:10.814884Z 0 [Warning] [MY-011070] [Server] '--sync-relay-log-info' is deprecated and will be removed in a future release.
2025-02-06T21:51:10.814900Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2025-02-06T21:51:10.816313Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.40) starting as process 9996
2025-02-06T21:51:10.837125Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=100663296. Please use innodb_redo_log_capacity instead.
2025-02-06T21:51:10.840611Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-02-06T21:51:13.356579Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-02-06T21:51:17.014743Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2025-02-06T21:51:17.019897Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2025-02-06T21:51:17.671062Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-02-06T21:51:17.671334Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-02-06T21:51:17.720883Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2025-02-06T21:51:17.721033Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: '8.0.40'  socket: ''  port: 3306  MySQL Community Server - GPL.
2025-02-06T21:51:28.845836Z 0 [Warning] [MY-011070] [Server] '--sync-relay-log-info' is deprecated and will be removed in a future release.
2025-02-06T21:51:28.847458Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.40) starting as process 10808
2025-02-06T21:51:28.863751Z 0 [Warning] [MY-013869] [InnoDB] Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.
2025-02-06T21:51:28.864906Z 0 [ERROR] [MY-000058] [Server] Unknown suffix '.' used for variable 'mysqlx-port' (value '0.0').
2025-02-06T21:51:28.865288Z 0 [Warning] [MY-000081] [Server] option 'mysqlx-port': unsigned value 0 adjusted to 1.
2025-02-06T21:51:28.865634Z 0 [ERROR] [MY-000077] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Error while setting value '0.0' to 'mysqlx-port'.
2025-02-06T21:51:28.866127Z 0 [ERROR] [MY-010746] [Server] Parsing options for plugin 'mysqlx' failed.
2025-02-06T21:51:28.868404Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-02-06T21:51:30.033105Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-02-06T21:51:31.780873Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2025-02-06T21:51:31.786979Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2025-02-06T21:51:31.843409Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-02-06T21:51:31.843739Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-02-06T21:51:31.853064Z 0 [Warning] [MY-000067] [Server] unknown variable 'loose_mysqlx_port=33060'.
2025-02-06T21:51:31.853527Z 0 [ERROR] [MY-000067] [Server] unknown variable 'mysqlx_port=0.0'.
2025-02-06T21:51:31.854039Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-02-06T21:51:32.926772Z 0 [System] [MY-010910] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Shutdown complete (mysqld 8.0.40)  MySQL Community Server - GPL.

How to repeat:
I don't have much information about it.
[10 Feb 12:05] MySQL Verification Team
Hi Mr. INV,

Thank you for your bug report.

However, let us inform you about this forum. This forum is dedicated to reports with fully repeatable test cases. Each of these test cases should consist of the set of SQL statements that always lead to the problem that you report.

You have not provided us with such a test case.

You have not provided us either with a full stacktrace ......

Beside that, there is a clear message that MySQL server has run of the memory that is available to it.

That is definitely not our bug.

Can't repeat.