Incremental Backup Preparation Mariabackup --prepare crashed [ERROR] mysqld got signal 6 ;

We have big database we are backing up we do full backup then full backup prepare and then incremental backup it worked fine by the time we are doing incremental backup prepare we experience this issue/error for the past 3 weeks. We`ve done upgrading versions from version 10.4.10 to 10.4.13 still the same issue/error we encounter.

2020-08-11 17:01:20 0x7f4b5ef8e700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.13/storage/innobase/log/log0recv.cc line 1520
InnoDB: Failing assertion: Unable to render embedded object: File (page ) not found.!page_is_comp(page) == dict_table_is_comp(index->table)
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.
200811 17:01:20 [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.4.13-MariaDB-1:10.4.13+maria~buster
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=1
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5932 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
mariabackup(my_print_stacktrace+0x2e)[0x559862857bfe]
mariabackup(handle_fatal_signal+0x54d)[0x5598623b48ed]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f4b781b9730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f4b776017bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f4b775ec535]
mariabackup(+0x5c340f)[0x55986203540f]
mariabackup(+0x5a5cc1)[0x559862017cc1]
mariabackup(+0xb6d6ed)[0x5598625df6ed]
mariabackup(+0x5a629f)[0x55986201829f]
mariabackup(+0x588fae)[0x559861ffafae]
mariabackup(+0xac319c)[0x55986253519c]
mariabackup(+0xc03600)[0x559862675600]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f4b781aefa3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f4b776c34cf]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /BackupDirectory
Resource Limits:
Fatal signal 11 while backtracing