mysqld got signal 11 - query from performance_schema.threads

Bug #1608486 reported by Milan Remenar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

We got this issue 3x on new Percona Server (GPL) 5.7.13-6-log, Release 6, Revision e3d58bb , On Centos 7 64 bit

08:46:53 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=1073741824
read_buffer_size=131072
max_used_connections=557
max_threads=1025
thread_count=12
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1512663 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x34bb560
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 = 7fc6b4a5cc80 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xef592b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0x79c091]
/lib64/libpthread.so.0(+0xf100)[0x7fc9ea261100]
/usr/sbin/mysqld(_ZN16cursor_by_thread8rnd_nextEv+0x64)[0xf881e4]
/usr/sbin/mysqld(_ZN13ha_perfschema8rnd_nextEPh+0x66)[0xf24b66]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x164)[0x7fead4]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x20)[0xc30590]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x147)[0xca1327]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x267)[0xc99ed7]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x17d)[0xd0b75d]
/usr/sbin/mysqld[0x75c15f]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x4697)[0xccd8d7]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x60d)[0xcd0a4d]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xcd140f]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1df)[0xcd2def]
/usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0xdb)[0xd78b8b]
/usr/sbin/mysqld[0xd8810e]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xf25f94]
/lib64/libpthread.so.0(+0x7dc5)[0x7fc9ea259dc5]
/lib64/libc.so.6(clone+0x6d)[0x7fc9e84aaced]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (34efd40): SELECT st.* FROM performance_schema.events_statements_current st JOIN performance_schema.threads thr ON thr.thread_id = st.thread_id WHERE thr.processlist_id = 91000
Connection ID (thread ID): 90985
Status: NOT_KILLED

Revision history for this message
Milan Remenar (milaner72) wrote :

This issue was caused 3x by query: SELECT st.* FROM performance_schema.events_statements_current st JOIN performance_schema.threads thr ON thr.thread_id = st.thread_id WHERE thr.processlist_id =

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.