Bug #77185 mysqld crash while applying a binlog event (delete query)
Submitted: 28 May 2015 19:35 Modified: 30 Jul 2015 11:21
Reporter: SAI KRISHNA TEJA MOKKAPATI Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.6.21 OS:Linux
Assigned to: CPU Architecture:Any
Tags: binlog, crash, delete

[28 May 2015 19:35] SAI KRISHNA TEJA MOKKAPATI
Description:
mysqld slave crashed while applying a  bin log event. More specifically a delete statement. Replication is row base. 

19:08:35 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=16777216
read_buffer_size=262144
max_used_connections=3
max_threads=500
thread_count=5
connection_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 407235 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f64b4000990
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 = 7f64df0b26a0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x9188f5]
/usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x6767a8]
/lib64/libpthread.so.0(+0xf710)[0x7f658e1f4710]
/usr/sbin/mysqld(_Z10unpack_rowPK14Relay_log_infoP5TABLEjPKhPK9st_bitmapPS5_PmS5_+0x226)[0x8d2ff6]
/usr/sbin/mysqld(_ZN14Rows_log_event24do_index_scan_and_updateEPK14Relay_log_info+0x110)[0x8a7210]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0xbbc)[0x8abffc]
/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x74)[0x8a61b4]
/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x18a)[0x8ebe8a]
/usr/sbin/mysqld[0x8ec894]
/usr/sbin/mysqld(handle_slave_sql+0xc6f)[0x8ee0df]
/usr/sbin/mysqld(pfs_spawn_thread+0x126)[0x993c46]
/lib64/libpthread.so.0(+0x79d1)[0x7f658e1ec9d1]
/lib64/libc.so.6(clone+0x6d)[0x7f658cf558fd]

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

How to repeat:
If you do an large un commited transaction on master and when slave tries sync the same , mysqld crashes.
[30 Jul 2015 11:21] MySQL Verification Team
Thank you for the report.
I'm not able to repeat this on latest builds and most likely duplicate of Bug #77261 . Please try latest build 5.6.26 and report us back if you are still seeing this issue with exact repeatable test case.

Thanks,
Umesh