Comment 1 for bug 1295672

InnoDB: Doing recovery: scanned up to log sequence number 147368420225
2014-03-21 12:58:41 8061 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 2014-03-21 12:58:48 7fb4d4f56700 InnoDB: Assertion failure in thread 140414643693312 in file page0zip.cc line 4357
InnoDB: Failing assertion: slot_rec
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:58:48 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=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=502
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 = 1614987 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8ca6d5]
/usr/sbin/mysqld(handle_fatal_signal+0x4c4)[0x645024]
/lib64/libpthread.so.0(+0xf710)[0x7fb7f5cca710]
/lib64/libc.so.6(gsignal+0x35)[0x7fb7f432b925]
/lib64/libc.so.6(abort+0x175)[0x7fb7f432d105]
/usr/sbin/mysqld[0x98459c]
/usr/sbin/mysqld[0x97ab89]
/usr/sbin/mysqld[0x97af6b]
/usr/sbin/mysqld[0x961578]
/usr/sbin/mysqld[0x9677fc]
/usr/sbin/mysqld[0xa384df]
/usr/sbin/mysqld[0xa79b28]
/usr/sbin/mysqld[0x9dd850]
/lib64/libpthread.so.0(+0x79d1)[0x7fb7f5cc29d1]
/lib64/libc.so.6(clone+0x6d)[0x7fb7f43e1b6d]
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.
140321 12:58:48 mysqld_safe mysqld from pid file /opt/mysql/dbprod/tools-q0.pid ended