LP #1353644: Server crash when "START TRANSACTION WITH CONSISTENT SNAPSHOT" / mysqldump --single-transaction is executed while binlog is disabled

**Reported in Launchpad by Daniel Guzmán Burgos last update 30-08-2014 05:57:52

This applies to PXC 5.6.19-67.0-56-log Percona XtraDB Cluster (GPL), Release 25.6, wsrep_25.6.r4111

When binlog is disabled, and START TRANSACTION WITH CONSISTENT SNAPSHOT" is executed, the server crash with the following stack:

18:47:24 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=0
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61058 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f56b8b65eb0
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 = 7f568ed24e00 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7f56b61d404c]
/usr/sbin/mysqld(handle_fatal_signal+0x3cb)[0x7f56b5f1aa2b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f56b43c5340]
/usr/sbin/mysqld(+0x6e4cd7)[0x7f56b617ecd7]
/usr/sbin/mysqld(+0x3a8a5a)[0x7f56b5e42a5a]
/usr/sbin/mysqld(Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3+0x1dd)[0x7f56b5fbeb8d]
/usr/sbin/mysqld(_Z28ha_start_consistent_snapshotP3THD+0x281)[0x7f56b5e47a51]
/usr/sbin/mysqld(_Z11trans_beginP3THDj+0x100)[0x7f56b6045910]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2b9b)[0x7f56b5fae0fb]
/usr/sbin/mysqld(+0x519ee8)[0x7f56b5fb3ee8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1280)[0x7f56b5fb5680]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x16c)[0x7f56b5fb78fc]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x31d)[0x7f56b5f78d3d]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x7f56b5f78de0]
/usr/sbin/mysqld(pfs_spawn_thread+0x140)[0x7f56b644cfb0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f56b43bd182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f56b38ca30d]

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

When binlog is enabled, the server doesn't crash

This applies only on PXC. Percona Server 5.6 doesn't seem to be affected by this issue.
Could be related with the following enhancement? https://blueprints.launchpad.net/percona-server/+spec/enhancements-for-start-transaction-with-consistent

PXC 5.6.15 doesn't seem to be affected