mysqld got signal 6 (10.6.18) innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

After we upgraded from mariadb 10.6.17 to 10.6.18 we often get this message:
mysqld got signal 6

2024-06-07 21:33:58 27735 [Warning] InnoDB: Could not free any blocks in the buffer pool! 1684787 blocks are in use and 0 free. Consider increasing innodb_buffer_pool_size.
2024-06-07 21:44:23 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/
240607 21:44:23 [ERROR] mysqld got signal 6 ;
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-ubu2004-log source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=19
max_threads=902
thread_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2117587 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...
stack_bottom = 0x0 thread_stack 0x49000
Printing to addr2line failed
/usr/sbin/mariadbd(my_print_stacktrace+0x32)[0x563a276dd0a2]
/usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x563a27189455]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f513c939420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f513c43d00b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f513c41c859]
/usr/sbin/mariadbd(+0x6879a1)[0x563a26dee9a1]
/usr/sbin/mariadbd(+0x680867)[0x563a26de7867]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x3d)[0x563a2767021d]
/usr/sbin/mariadbd(_ZN5tpool4task7executeEv+0x3a)[0x563a27670ffa]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x5f)[0x563a2766e9ef]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6df4)[0x7f513c813df4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f513c92d609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f513c519353]
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...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 128044 128044 processes
Max open files 32768 32768 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 128044 128044 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g – %E

Kernel version: Linux version 5.4.0-173-generic (buildd@lcy02-amd64-101) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #191-Ubuntu SMP Fri Feb 2 13:55:07 UTC 2024