MariaDB 10.6.11 - InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/trx/trx0trx.cc line 1270

Hello all,

one of our MariaDB instances keeps crashing once in a while with errors like the on below.
The application connecting to the database is pimcore.

We already checked/tried these things:

• checked hardware (CPU/RAM)
• checked configuration with MySQL Tuner
• upgrade from 10.5.9 to 10.6.10
• another update from MariaDB 10.6.10 to 10.6.11
• build a new instance to seperate the databases
• developer checked queries (also if too many queries at same time)
• updates of pimcore

We are running out of ideas and would be very thankful for support.

This is the error-message from the last crash:

2023-10-04 15:29:03 0x7fb205f1e700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/trx/trx0trx.cc line 1270
InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0
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 mariadbd 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.
231004 15:29:03 [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.6.11-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=39
max_threads=52
thread_count=36
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 245554 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fb1e00e49a8
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 = 0x7fb205f1dcc0 thread_stack 0x49000
/DBA/mysql/SQL/5.7.latest/bin/mysqld(my_print_stacktrace+0x2e)[0x56512259429e]
/DBA/mysql/SQL/5.7.latest/bin/mysqld(handle_fatal_signal+0x307)[0x565121f5b947]
2023-10-04 15:29:05 0x7fb230ed4700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/trx/trx0trx.cc line 1270
InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0
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 mariadbd 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.