Comment 11 for bug 1328432

We ran into a very similar issue on a production server. The line numbers are different, but here's some information from our crash.

We have plenty of disk space (for both our data and tmp) and plenty of memory. So that doesn't seem to be the cause for our crash.

Percona Server 5.6.33-79.0 on Ubuntu 14.04.5 LTS using Kernel 3.13.0-24-generic

2016-11-25 23:53:21 7f012806a700 InnoDB: Assertion failure in thread 139642943219456 in file os0file.cc line 5241
InnoDB: Failing assertion: slot != NULL
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.
23:53:21 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=268435456
read_buffer_size=131072
max_used_connections=10429
max_threads=40002
thread_count=4851
connection_count=4849
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 87862134 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8d777c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x659df1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f4d6b6ef330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4d6ab30c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4d6ab34028]
/usr/sbin/mysqld[0x98d67e]
/usr/sbin/mysqld[0xab0611]
/usr/sbin/mysqld[0x9fa6f0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f4d6b6e7184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4d6abf437d]
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.