Bug #80015 MySQL 5.6.18 mysqld got signal 11

Description:
My dedicated MySQL Server 5.6.18 crashed which has not happened before.

This was the stack trace :

22:08:04 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=4294967296
read_buffer_size=1048576
max_used_connections=96
max_threads=500
thread_count=11
connection_count=9
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5737155 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fdbad4f0b40
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 = 7fdb9bcb1e0f thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x93f215]
/usr/sbin/mysqld(handle_fatal_signal+0x401)[0x6b3101]
/lib64/libpthread.so.0(+0xf7c0)[0x7fe76ea697c0]
/usr/sbin/mysqld(_ZNK12Field_string4typeEv+0x19)[0x81b309]
/usr/sbin/mysqld(_Z10field_convP5FieldS0_+0x8c)[0x82135c]
/usr/sbin/mysqld(_ZN10Item_field13save_in_fieldEP5Fieldb+0x56)[0x5fc136]
/usr/sbin/mysqld(_Z12sp_eval_exprP3THDP5FieldPP4Item+0x86)[0x6b3506]
/usr/sbin/mysqld(_ZN9sp_cursor24Select_fetch_into_spvars9send_dataER4ListI4ItemE+0x5b)[0x6bf46b]
/usr/sbin/mysqld(_ZN19Materialized_cursor5fetchEm+0x4d)[0x7074cd]
/usr/sbin/mysqld(_ZN9sp_cursor5fetchEP3THDP4ListI11sp_variableE+0xcf)[0x6bf17f]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x782)[0x6b9922]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x749)[0x6bb699]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x118d)[0x73688d]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x60)[0x86fbe0]
/usr/sbin/mysqld(_ZN12sp_lex_instr23reset_lex_and_exec_coreEP3THDPjb+0x278)[0x86ff58]
/usr/sbin/mysqld(_ZN12sp_lex_instr29validate_lex_and_execute_coreEP3THDPjb+0x93)[0x871553]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x190)[0x8721c0]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x782)[0x6b9922]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x749)[0x6bb699]
/usr/sbin/mysqld(_ZN14Event_job_data7executeEP3THDb+0x893)[0x7e3213]
/usr/sbin/mysqld(_ZN19Event_worker_thread3runEP3THDP28Event_queue_element_for_exec+0xe1)[0x8c1751]
/usr/sbin/mysqld(event_worker_thread+0x54)[0x8c1814]
/usr/sbin/mysqld(pfs_spawn_thread+0x126)[0x9d6576]
/lib64/libpthread.so.0(+0x77b6)[0x7fe76ea617b6]
/lib64/libc.so.6(clone+0x6d)[0x7fe76d7ddd6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (61fcf4a0): CALL drop_detailed_rows_sp(0,20000)
Connection ID (thread ID): 6564540
Status: NOT_KILLED

Any information on this would be great. Thanks!

How to repeat:
I do not know. The stack trace seems to be caused from a scheduled event with a procedure call.

Hello Mahmoud Youssef,

Thank you for the report.
This is duplicate of internally reported bug which is fixed in 5.6.19. 
Please upgrade to latest GA and let us know if you are still having this issue. Per change log:

Noted in 5.6.19 changelog. 

Concurrent execution of a FLUSH TABLE operation and a stored program 
that used a cursor could cause a server exit. 

Thanks,
Umesh

Hi Umesh,

Thanks very much for your quick response and resolve.

Can you post a link to that initial bug report? 

5.6.19 Changelog : 
Concurrent execution of a FLUSH TABLE operation and a stored program that used a cursor could cause a server exit. (Bug #18158639)

However, I cannot find that bug when searching in the bug system. (#18158639)

Bug #18158639 is an internal bug and hence not visible but changelog is present in release notes.

5.6.19 Changelog : 
Concurrent execution of a FLUSH TABLE operation and a stored program that used a cursor could cause a server exit.