mysqld segmentation fault while "userstat = 1" and replication slave configured

[Eugene]

If mysql slave configured with option:

"userstat = 1"

mysqld crashed:

120615 13:01:08 [Note] Plugin 'FEDERATED' is disabled.
120615 13:01:08 InnoDB: The InnoDB memory heap is disabled
120615 13:01:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120615 13:01:08 InnoDB: Compressed tables use zlib 1.2.3
120615 13:01:08 InnoDB: Using Linux native AIO
120615 13:01:08 InnoDB: Initializing buffer pool, size = 2.0G
120615 13:01:08 InnoDB: Completed initialization of buffer pool
120615 13:01:08 InnoDB: highest supported file format is Barracuda.
120615 13:01:08 InnoDB: Restoring buffer pool pages from ib_lru_dump
120615 13:01:08 Percona XtraDB (http://www.percona.com) 1.1.8-rel26.0 started; log sequence number 1597945
120615 13:01:08 InnoDB: Completed reading buffer pool pages (requested: 179, read: 36)
120615 13:01:08 [Note] Server hostname (bind-address): '(null)'; port: 3307
120615 13:01:08 [Note] - '(null)' resolves to '0.0.0.0';
120615 13:01:08 [Note] - '(null)' resolves to '::';
120615 13:01:08 [Note] Server socket created on IP: '0.0.0.0'.
120615 13:01:09 [Note] Slave SQL thread initialized, starting replication in log 'bin.000065' at position 970449520, relay log '/mysql-tmp/mdb3-t/relay-log/relay.000002' position: 247
09:01:09 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.

key_buffer_size=33554432
read_buffer_size=4194304
max_used_connections=0
max_threads=50
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 442980 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7ba4000990
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 = 7f7e55c61e78 thread_stack 0x60000
120615 13:01:09 [Note] Slave I/O thread: connected to master '*****@*****:3306',replication started in log 'bin.000065' at position 1049656715
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a5d85]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x680e04]
/lib64/libpthread.so.0(+0xf4a0)[0x7f7e559454a0]
/usr/sbin/mysqld[0x622f96]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x624a82]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x58b10a]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xe58)[0x7278d8]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x5294e5]
/usr/sbin/mysqld[0x52dfc9]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x52f399]
/lib64/libpthread.so.0(+0x77f1)[0x7f7e5593d7f1]
/lib64/libc.so.6(clone+0x6d)[0x7f7e54bc3ccd]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

[Alexey Kopytov (akopytov)]

Thank you for your bug report. This problem has already been reported as bug #1008278 and we are going to fix it in the next release.