Percona Server debug crashes with assertion table->key_read == 0

[Ovais Tariq]

Percona Server version 5.6.32

mysqld-debug: /mnt/workspace/percona-server-5.6-debian-binary/label_exp/debian-jessie-64bit/percona-server-5.6-5.6.32-78.1/sql/sql_base.cc:1475: void close_thread_table(THD*, TABLE**): Assertion `table->key_read == 0' failed.
07:13:52 UTC - 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.
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=2
max_threads=4098
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1646957 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x4c9ad540
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 = 40c7e58 thread_stack 0x30000
/usr/sbin/mysqld-debug(my_print_stacktrace+0x35)[0xa97da3]
/usr/sbin/mysqld-debug(handle_fatal_signal+0x42d)[0x713091]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8f0)[0x4e3b8f0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x6de5077]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x6de6458]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e266)[0x6dde266]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e312)[0x6dde312]
/usr/sbin/mysqld-debug(_Z18close_thread_tableP3THDPP5TABLE+0x68)[0x75194a]
/usr/sbin/mysqld-debug[0x751374]
/usr/sbin/mysqld-debug(_Z19close_thread_tablesP3THD+0x35a)[0x7518ce]
/usr/sbin/mysqld-debug(_Z21mysql_execute_commandP3THD+0x8296)[0x7cd59c]
/usr/sbin/mysqld-debug(_Z11mysql_parseP3THDPcjP12Parser_state+0x589)[0x7d0888]
/usr/sbin/mysqld-debug(_Z16dispatch_command19enum_server_commandP3THDPcj+0xcc3)[0x7c2720]
/usr/sbin/mysqld-debug(_Z10do_commandP3THD+0x3bb)[0x7c161e]
/usr/sbin/mysqld-debug(_Z24do_handle_one_connectionP3THD+0x24f)[0x789c0c]
/usr/sbin/mysqld-debug(handle_one_connection+0x33)[0x7896c8]
/usr/sbin/mysqld-debug(pfs_spawn_thread+0x147)[0xae2cdf]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80ca)[0x4e340ca]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x6e988ad]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (5014e970): is an invalid pointer

[Laurynas Biveinis (laurynas-biveinis)]

Can you provide further information? Configuration, testcase, how repeatable is this?

[Ovais Tariq (ovais-tariq)]

Laurynas, it is consistently reproducible for the test case listed here: https://bugs.launchpad.net/percona-server/+bug/1635927

I was trying to run valgrind with mysqld-debug but it kept on crashing

[Roel Van de Paar (roel11)]

http://bugs.mysql.com/bug.php?id=74490

[Roel Van de Paar (roel11)]

FYI;

[roel@localhost ~]$ vi errorlog # paste in error log above
[roel@localhost ~]$ ~/percona-qa/text_string.sh errorlog
table->key_read == 0
[roel@localhost ~]$ grep 'table->key_read == 0' ~/percona-qa/known_bugs.strings
table->key_read == 0 ## http://bugs.mysql.com/bug.php?id=74490

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3585