211006 16:52:06 [ERROR] mysqld got signal 6 ;
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.6.4-MariaDB
key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 369652 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f6cc5e07c58
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 = 0x7f6ded0f3548 thread_stack 0x49000
mysys/stacktrace.c:213(my_print_stacktrace)[0x56031ade1efd]
sql/signal_handler.cc:225(handle_fatal_signal)[0x56031a948901]
libc_sigaction.c:0(__restore_rt)[0x7f6ded1fb760]
nptl/pthread_kill.c:46(__pthread_kill_internal)[0x7f6ded248763]
posix/raise.c:27(__GI_raise)[0x7f6ded1fb6b6]
stdlib/abort.c:81(__GI_abort)[0x7f6ded1e57d3]
posix/libc_fatal.c:155(__libc_message)[0x7f6ded23ca27]
debug/fortify_fail.c:25(__GI___fortify_fail)[0x7f6ded2d9d7a]
:0(__stack_chk_fail_local)[0x7f6ded2d9d46]
mysys_ssl/my_md5.cc:92(my_md5)[0x56031ab42d05]
bits/string_fortified.h:29(find_or_create_digest(PFS_thread*, sql_digest_storage const*, char const*, unsigned int))[0x56031ab643ff]
perfschema/pfs.cc:5452(pfs_end_statement_v1)[0x56031ab5de5a]
*** stack smashing detected ***: terminated