(xenial package only) xtradb-cluster-server SIGSEGV in find_or_create_digest

[Jochen]

Running a unit test, which alters between create/alter table statements and inserting into a log table I get a segfault. I can reproduce this every time, but it crashes at different positions.

Backtrace:
---------
13:22:34 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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=161
max_threads=507
thread_count=123
connection_count=74
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 218365 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2157230
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 = 7f44f4917e38 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x91d4bb]
/usr/sbin/mysqld(handle_fatal_signal+0x49a)[0x68aefa]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)[0x7f5f14ca53d0]
/lib/x86_64-linux-gnu/libc.so.6(+0x14d6f2)[0x7f5f141776f2]
/usr/sbin/mysqld(_Z21find_or_create_digestP10PFS_threadPK18sql_digest_storagePKcj+0x29d)[0x9356ed]
/usr/sbin/mysqld[0x960143]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x589)[0x719739]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x339)[0x71cee9]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x182)[0x6e18c2]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6e1ab0]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0x95be33]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f5f14c9b6fa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5f14130b5d]

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

You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
160630 15:22:35 mysqld_safe Number of processes running now: 0
160630 15:22:35 mysqld_safe WSREP: not restarting wsrep node automatically
160630 15:22:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
---------

When trying to find the last working version I found that packages for trusty seemed to be unaffected.
bad: percona-xtradb-cluster-server-5.6_5.6.30-25.16-1.xenial_amd64.deb
good: percona-xtradb-cluster-server-5.6_5.6.30-25.16-1.trusty_amd64.deb

./good
./good/percona-xtradb-cluster-server-5.6_5.6.26-25.12-1.trusty_amd64.deb
./good/percona-xtradb-cluster-server-5.6_5.6.30-25.16-1.trusty_amd64.deb
./good/percona-xtradb-cluster-server-5.6_5.6.25-25.12-1.vivid_amd64.deb
./good/percona-xtradb-cluster-server-5.6_5.6.21-25.8-938.trusty_amd64.deb
./bad
./bad/percona-xtradb-cluster-server-5.6_5.6.26-25.12-1.vivid_amd64.deb
./bad/percona-xtradb-cluster-server-5.6_5.6.28-25.14-1.wily_amd64.deb
./bad/percona-xtradb-cluster-server-5.6_5.6.27-25.13-1.wily_amd64.deb
./bad/percona-xtradb-cluster-server-5.6_5.6.30-25.16-1.xenial_amd64.deb
./bad/percona-xtradb-cluster-server-5.6_5.6.29-25.15-1.xenial_amd64.deb

[Krunal Bauskar (krunal-bauskar)]

Given that you could reproduce it everytime can you help us with

a. Reproducible tcs.
b. configuration of node(s).

[Launchpad Janitor (janitor)]

[Expired for Percona XtraDB Cluster because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

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