Got this error in error.log
2020-11-05 16:42:09 0x7ef37c66c700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.13/storage/innobase/row/row0ins.cc line 231
InnoDB: Failing assertion: !cursor->index->is_committed()
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: about forcing recovery.
201105 16:42:09 [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-log
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5959249 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7ef21402d348
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 0x7ef37c66bcd8 thread_stack 0x40000
- buffer overflow detected ***: /usr/sbin/mysqld terminated
So I'm here to report it)
The environment (Operating system = Debian GNU/Linux 10 (buster), MariaDB version = Server version: 10.4.13-MariaDB-1:10.4.13+maria~buster-log)