/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x688d38]
/usr/sbin/mysqld[0x593e7a]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa8c)[0x59870c]
/usr/sbin/mysqld[0x517a0a]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x44d)[0x51b37d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f3dd1eaad5d]
/usr/sbin/mysqld[0x5106a9]
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.
150313 00:53:40 mysqld_safe mysqld from pid file /var/lib/mysql/buzz.chocchip.com.au.pid ended
150313 00:55:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150313  0:55:13 [Note] Plugin 'FEDERATED' is disabled.
150313  0:55:13 InnoDB: The InnoDB memory heap is disabled
150313  0:55:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150313  0:55:13 InnoDB: Compressed tables use zlib 1.2.3
150313  0:55:13 InnoDB: Using Linux native AIO
150313  0:55:13 InnoDB: Initializing buffer pool, size = 128.0M
150313  0:55:13 InnoDB: Completed initialization of buffer pool
150313  0:55:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1129263120077
150313  0:55:13  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1129263127583
InnoDB: Error: trying to access page number 4294965119 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
150313  0:55:14  InnoDB: Assertion failure in thread 140414333122304 in file fil0fil.c line 4578
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.
13:55:14 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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 338550 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.