Comment 4 for bug 1134892

We have also come across this bug as described here. I have a snapshot of our db in a state where I can consistently crash the server with a simple update statement. Please advise if I can provide more detailed information.

Things of note:
* The update works fine if I disable foreign key checks
* Forcing a recreation the foreign key seems to help get past this crash in some cases even though the foreign key itself remains the same
* Observations indicate that the length of the string used as a foreign key could be relevant, or possibly the contents of the string.

example update statement causing the crash:
mysql> update appglu_storage_files set url = concat('1', url);
ERROR 2013 (HY000): Lost connection to MySQL server during query

From error log:

130307 18:10:46 InnoDB: Assertion failure in thread 140317682054912 in file rem0rec.c line 564
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:10:46 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=33554432
read_buffer_size=8388608
max_used_connections=5
max_threads=5000
thread_count=4
connection_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 51296010 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x6305bb0
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 = 7f9e41982e70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7d357e]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0x6aa084]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f9e40ba3cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f9e4080b425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f9e4080eb8b]
/usr/sbin/mysqld[0x815238]
/usr/sbin/mysqld(wsrep_rec_get_foreign_key+0x6c)[0x81744c]
/usr/sbin/mysqld(wsrep_append_foreign_key+0x407)[0x803907]
/usr/sbin/mysqld[0x93b18f]
/usr/sbin/mysqld[0x93ca7a]
/usr/sbin/mysqld[0x8315dc]
/usr/sbin/mysqld[0x832466]
/usr/sbin/mysqld[0x8359ce]
/usr/sbin/mysqld[0x81f1a1]
/usr/sbin/mysqld[0x804a02]
/usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x66)[0x6b1ae6]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x131d)[0x61f59d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x28ca)[0x5a789a]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x30c)[0x5acb0c]
/usr/sbin/mysqld[0x5ad440]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1a80)[0x5afba0]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x5afff9]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x157)[0x64ad57]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x64af01]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f9e40b9be9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9e408c8cbd]

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

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
130307 18:10:46 mysqld_safe Number of processes running now: 0
130307 18:10:46 mysqld_safe WSREP: not restarting wsrep node automatically
130307 18:10:46 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld-appglu.pid ended