220603 21:38:01 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

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.5.15-MariaDB-1:10.5.15+maria~buster-log
key_buffer_size=67108864
read_buffer_size=4194304
max_used_connections=118
max_threads=802
thread_count=48
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6655926 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7eeb0c0008e8
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 = 0x7f02413e4d58 thread_stack 0x40000
2022-06-03 21:38:05 0x7eed537fe700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.15/storage/innobase/dict/dict0dict.cc line 1248
InnoDB: Failing assertion: table->can_be_evicted
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
Fatal signal 6 while backtracing