Customer reports server crashing repeatedly during crash recovery. The cause of the initial crash is still unkown, but during subsequent restarts it crashes with:

2020-04-09 21:36:15 0 [Note] InnoDB: Starting final batch to recover 11194 pages from redo log.
200409 21:36:15 [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.3.16-MariaDB-log
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=0
max_threads=1002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2268410 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x562a0648764e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x562a05f28dff]
sigaction.c:0(__restore_rt)[0x7f2fd0214680]
/usr/sbin/mysqld(+0x99b350)[0x562a0613d350]
/usr/sbin/mysqld(+0x99aa7d)[0x562a0613ca7d]
/usr/sbin/mysqld(+0x99b26a)[0x562a0613d26a]
/usr/sbin/mysqld(+0x978eea)[0x562a0611aeea]
/usr/sbin/mysqld(+0x979e23)[0x562a0611be23]
/usr/sbin/mysqld(+0x4c8739)[0x562a05c6a739]
/usr/sbin/mysqld(+0xab2ac8)[0x562a06254ac8]
/usr/sbin/mysqld(+0xb19431)[0x562a062bb431]
/usr/sbin/mysqld(+0xa25cf8)[0x562a061c7cf8]
/lib64/libpthread.so.0(+0x7dd5)[0x7f2fd020cdd5]
/lib64/libc.so.6(clone+0x6d)[0x7f2fce5afb3d]