Bug found in Percona Server Version: 5.6.34-79.1-1.jessie

Hi,

Today we encountered bug in Percona Server Version: 5.6.34-79.1-1.jessie server.
Mysql service was unavailable for few seconds during bug logging process.

Attached mysql-error.log with bug details. Please help.

Here are few bug related logs.

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=414
max_threads=502
thread_count=81
connection_count=81
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 232495 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x36fb450
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 = 7fa997040e88 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8c10bc]
/usr/sbin/mysqld(handle_fatal_signal+0x469)[0x649249]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fb15df7d8d0]
/usr/sbin/mysqld(_ZN8MDL_lock11Ticket_list13remove_ticketEP10MDL_ticket+0x11)[0x63b981]
/usr/sbin/mysqld(_ZN8MDL_lock13remove_ticketEMS_NS_11Ticket_listEP10MDL_ticket+0x88)[0x63be48]
/usr/sbin/mysqld(_ZN11MDL_context12release_lockE17enum_mdl_durationP10MDL_ticket+0x1a)[0x63ceea]
/usr/sbin/mysqld(_ZN18Global_backup_lock18release_protectionEP3THD+0x1c)[0x7bee6c]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG6commitEP3THDb+0x4c5)[0x86e645]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDbb+0x310)[0x591290]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x29)[0x751679]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2eb9)[0x6c9c99]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5e8)[0x6ccfe8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xd2b)[0x6ce3cb]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a2)[0x69b1d2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x69b270]
/usr/sbin/mysqld(pfs_spawn_thread+0x146)[0x8fc596]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fb15df760a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb15bfb662d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa86246b900): is an invalid pointer
Connection ID (thread ID): 46143427
Status: NOT_KILLED

bug.txt (10.8 KB)

Is there any reason for using such an old PS version (5.6.34 vs latest 5.6.51)?
Can you upgrade and check if similar problem occurs with more recent versions?