mysterious crash-and-restart of percona server 5.5 on several servers

[Virginia Banh]

We have mysterious crush-and-restart of percona mysql 5.5 on several servers with such info in the errorlog:
------------------------------------------
Version: '5.5.25a-27.1-log' socket: '/data/mysql/mysql.sock' port: 3306 Percona Server (GPL), Release rel27.1, Revision 277
02:37:31 UTC - mysqld got signal 8 ;
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=2097152
max_used_connections=4
max_threads=900
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3730200 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2367eb80
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 = 7f846e618e58 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a8d05]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x685304]
/lib64/libpthread.so.0[0x367d20f500]
/usr/sbin/mysqld(_ZN12ha_partition21min_rows_for_estimateEv+0x61)[0x956f31]
/usr/sbin/mysqld(_ZN12ha_partition16records_in_rangeEjP12st_key_rangeS1_+0x35)[0x956f75]
/usr/sbin/mysqld[0x73cee7]
/usr/sbin/mysqld[0x73cc14]

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

[Virginia Banh (virginia-banh)]

This is the version we have on the server:

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 47498
Server version: 5.5.25a-27.1-log Percona Server (GPL), Release rel27.1, Revision 277

[Virginia Banh (virginia-banh)]

and it seems like this issue still exists in version 5.5.27, and please advise.

Regards,
Virginia

[Alexey Kopytov (akopytov)]

The version string "5.5.25a-27.1" means it is version 5.5.25a, so it is still affected by the bug.

[Virginia Banh (virginia-banh)]

we just upgraded our slave servers to the latest version, and so far haven't encountered this issue again. We will keep you posted if we see this error again.

Here is the latest version that we upgraded our servers to:

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 5655
Server version: 5.5.28-29.3-log Percona Server (GPL), Release rel29.3, Revision 388

Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.

Regards,
Virginia