One of our production DB server was constantly crashing. Service is extensively using temporary tables in sessions and randomly server would crash if we were selecting information from GLOBAL_TEMPORARY_TABLES view.
Select:
SELECT engine, data_length, index_length FROM GLOBAL_TEMPORARY_TABLES;
How to reproduce issue:
1. In loop start selecting data from GLOBAL_TEMPORARY_TABLES
2. In second session - start creating lots of temporary tables
Simple script (sorry not mysql test suite):
1. In one session start such simple select (better reproducible if several sessions do the same):
watch -n 0.1 "mysql information_schema -e 'SELECT engine, data_length, index_length FROM GLOBAL_TEMPORARY_TABLES'"
2. In another session start creating lots of temporary tables (tested with 300, but usually mysql crashes faster, from time to time creation has to be repeated):
```
echo "Create temporary table a1(a varchar(256));Create temporary table a2(a varchar(256));Create temporary table a3(a varchar(256));Create temporary table a4(a varchar(256));Create temporary table a5(a varchar(256));Create temporary table a6(a varchar(256));Create temporary table a7(a varchar(256));Create temporary table a8(a varchar(256));Create temporary table a9(a varchar(256));Create temporary table a10(a varchar(256));Create temporary table a11(a varchar(256));Create temporary table a12(a varchar(256));Create temporary table a13(a varchar(256));Create temporary table a14(a varchar(256));Create temporary table a15(a varchar(256));Create temporary table a16(a varchar(256));Create temporary table a17(a varchar(256));Create temporary table a18(a varchar(256));Create temporary table a19(a varchar(256));Create temporary table a20(a varchar(256));Create temporary table a21(a varchar(256));Create temporary table a22(a varchar(256));Create temporary table a23(a varchar(256));Create temporary table a24(a varchar(256));Create temporary table a25(a varchar(256));Create temporary table a26(a varchar(256));...." | mysql test
```
Mysql error log:
```
11:29:47 UTC - mysqld got signal 11 ;
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.
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=11
max_threads=4098
thread_count=8
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1646765 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fec12b09000
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 = 7fec690dae48 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8ba78c]
/usr/sbin/mysqld(handle_fatal_signal+0x469)[0x646369]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fec6b4a48d0]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x3b2)[0x7464f2]
/usr/sbin/mysqld(_Z19open_table_uncachedP3THDPKcS2_S2_bb+0x188)[0x67ab18]
/usr/sbin/mysqld[0x7144b7]
/usr/sbin/mysqld(_Z26mysql_create_table_no_lockP3THDPKcS2_P24st_ha_create_informationP10Alter_infojPb+0xf8)[0x714ad8]
/usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xcc)[0x714c6c]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4f80)[0x6c8c50]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5d8)[0x6c9dd8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x109b)[0x6cb52b]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a2)[0x6981a2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x698240]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0x8f5a83]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fec6b49d0a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fec6946f87d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7febd541d010): is an invalid pointer
Connection ID (thread ID): 430
Status: NOT_KILLED
```
We also have core dump, stack trace from core dump is in attached file.
We also have core dump from original crash, stack trace is actually different and is caused by null reference during `SELECT engine, data_length, index_length FROM GLOBAL_TEMPORARY_TABLES` execution
We're using percona 5.6.29-76.2 (latest 5.6 at the moment)