corruption in the InnoDB tablespace

2020-12-31 9:45:33 17 [ERROR] InnoDB: Page old data size 10435 new data size 10508, page old max ins size 5815 new max ins size 5742
2020-12-31 9:45:33 17 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2020-12-31 9:48:48 14 [ERROR] InnoDB: Page old data size 9785 new data size 9789, page old max ins size 6465 new max ins size 6461
2020-12-31 9:48:48 14 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2020-12-31 9:48:49 16 [ERROR] InnoDB: Page old data size 10901 new data size 10905, page old max ins size 5349 new max ins size 5345
2020-12-31 9:48:49 16 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2020-12-31 9:48:50 14 [ERROR] InnoDB: Page old data size 7235 new data size 7239, page old max ins size 9016 new max ins size 9012
2020-12-31 9:48:50 14 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2020-12-31 09:48:50 0x7f931f435700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/btr/btr0cur.cc line 4467
InnoDB: Failing assertion: rec
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.
201231 9:48:50 [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.