We are experiencing a critical issue with MySQL 8.4.0 configured as part of an InnoDB Cluster with Group Replication.
On 2025-04-17 at 18:54:47 UTC, the mysqld process crashed with exception code 0xc0000005 (Access Violation). According to the error log, the issue appears to originate from group_replication.dll. Here's a snippet from the backtrace:
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
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...
7ffe151f14f3 VCRUNTIME140.dll!memcpy()
7ffde936250f group_replication.dll!???
7ffde9365824 group_replication.dll!???
7ffde938f009 group_replication.dll!???
7ffde93904c0 group_replication.dll!???
7ffde947dede group_replication.dll!???
7ffde947d299 group_replication.dll!???
7ffde94449e0 group_replication.dll!???
7ffde946da4a group_replication.dll!???
7ffde946d2ba group_replication.dll!???
7ffde946e08d group_replication.dll!???
7ffde946e1c6 group_replication.dll!???
7ff69997b1f9 mysqld.exe!?init_state_maps@@YA_NPEAVMY_CHARSET_LOADER@@PEAUCHARSET_INFO@@@Z()
7ff6993cc39c mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7ffe1c32268a ucrtbase.dll!_o_exp()
7ffe20077ac4 KERNEL32.DLL!BaseThreadInitThunk()
7ffe201aa8c1 ntdll.dll!RtlUserThreadStart()
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.