mariadb10.6.18 InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.

A dump file appeared during the runtime of mysqld.exe，Please refer to the attachment for specific information.

2024-06-25 1:46:21 103 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:46:31 112 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:46:31 113 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:46:41 133 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:46:51 139 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:47:01 140 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:47:11 141 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 1:47:21 143 [Warning] Access denied for user 'ޔ^p?'?Vf?J>???'@'192.168.1.91' (using password: YES)
2024-06-25 2:21:00 197 [Warning] InnoDB: Could not free any blocks in the buffer pool! 129856 blocks are in use and 0 free. Consider increasing innodb_buffer_pool_size.
2024-06-25 2:33:44 0 [Warning] InnoDB: Long wait (150 seconds) for dict_sys.latch
2024-06-25 2:36:14 0 [Warning] InnoDB: Long wait (300 seconds) for dict_sys.latch
2024-06-25 2:38:44 0 [Warning] InnoDB: Long wait (450 seconds) for dict_sys.latch
2024-06-25 2:41:14 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
240625 2:41:14 [ERROR] mysqld got exception 0x80000003 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.6.18-MariaDB-log source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=173
max_threads=65537
thread_count=163
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1082300030 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
server.dll!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
server.dll!json_valid()
server.dll!json_valid()
server.dll!json_valid()
ntdll.dll!TpReleaseWork()
ntdll.dll!RtlInitializeResource()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\DS\DS Server\mysql\data
Minidump written to C:\DS\DS Server\mysql\data\mysqld.dmp