MySQL restarts - mysqld got signal 11 ;

[Mark Phillips]

We host a web app using MySQL on AWS RDS. We recently upgraded to MySQL8 (8.0.28) and since then we are seeing the server restart itself approximately every 5-7 days with the following error.

========
2024-04-22T14:28:25Z mysqld got signal 11 ; ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x152666551800
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...
2024-04-22T14:28:25.081395Z 47526151 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2024-04-22T14:28:25.087136Z 47526152 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2024-04-22T14:28:25.111052Z 47526153 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2024-04-22T14:28:25.122618Z 47526154 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
stack_bottom = 1525b9a4b210 thread_stack 0x40000
2024-04-22T14:28:25.141865Z 47526155 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x151bd7e]
/rdsdbbin/mysql/bin/mysqld(print_fatal_signal(int)+0x276) [0xc179e6]
/rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0x7c) [0xc17c7c]
/lib64/libpthread.so.0(+0x118e0) [0x1533428648e0]
/rdsdbbin/mysql/bin/mysqld(has_external_table(Table_ref*)+0x32) [0xb2a512]
/rdsdbbin/mysql/bin/mysqld(Sql_cmd_dml::execute(THD*)+0x66b) [0xb3246b]
/rdsdbbin/mysql/bin/mysqld(mysql_execute_command(THD*, bool)+0x938) [0xaf39f8]
/rdsdbbin/mysql/bin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x587) [0xaf74f7]
/rdsdbbin/mysql/bin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x19df) [0xaf95ef]
/rdsdbbin/mysql/bin/mysqld(do_command(THD*)+0x1c9) [0xafa059]
/rdsdbbin/mysql/bin/mysqld() [0xc18b8f]
/rdsdbbin/mysql/bin/mysqld() [0x18cedbf]
/lib64/libpthread.so.0(+0x744b) [0x15334285a44b]
/lib64/libc.so.6(clone+0x3f) [0x15334203f52f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
====

It is always the same query in the error log(but on different databases) which is causing the error, however, when we run the query manually, it is fine. It feels like it is only in certain circumstances, e.g. hitting some kind of memory limit and causing it to fall over? I have read this could be an OS problem causing the OS to run out of memory and kill MySQL.

Can anyone advise? Should we start by reducing the amount of memory MySQL is trying to use, and if so, how best to do that?