MariaDB 10.4.19 reboots itself and gets message "[ERROR] mysqld got signal 6"

I'm running MariaDB 10.4.19 on CentOS 7.7.1908. Almost every day my database get that error on the log and reboots, after that it works fine but after a few hours or days the service restarts again. Can you help me find out what causes this error and its possible solution?

Thanks.

The following text is on the log:

2021-07-07 19:40:31 0x7f19c92f7700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.19/storage/innobase/lock/lock0lock.cc line 6942 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. 210707 19:40:31 [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.8-MariaDB-log key_buffer_size=131072 read_buffer_size=1048576 max_used_connections=168 max_threads=552 thread_count=101 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1144166 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.