MySQL Server Crashes in Prepared Statements when Using Cursor Protocol (Doc ID 1459681.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Server - Version 5.0 to 5.5 [Release 5.0 to 5.5]
Information in this document applies to any platform.

Symptoms

When attempting to run a prepared select statement using the cursor protocol the following error occurs.

ERROR
-----------------------
120507 15:57:32 - 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=4194304
max_used_connections=3246
max_threads=5000
thread_count=387
connection_count=387
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 45211257 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2aace4094b60
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 = 0x4e4140d0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c9669]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fd889]
/lib64/libpthread.so.0[0x39fec0e4c0]
/usr/sbin/mysqld(_ZN5Field10make_fieldEP10Send_field+0x19)[0x66c939]
/usr/sbin/mysqld(_ZN10Item_field10make_fieldEP10Send_field+0x26)[0x68f0f6]
/usr/sbin/mysqld(_ZN8Protocol24send_result_set_metadataEP4ListI4ItemEj+0x35c)[0x50c86c]
/usr/sbin/mysqld(_ZN11select_send24send_result_set_metadataER4ListI4ItemEj+0x1d)[0x5493fd]
/usr/sbin/mysqld(_ZN28Select_fetch_protocol_binary24send_result_set_metadataER4ListI4ItemEj+0x2e)[0x5862fe]
/usr/sbin/mysqld(_ZN19Materialized_cursor4openEP4JOIN+0xf4)[0x782c54]
/usr/sbin/mysqld(_Z17mysql_open_cursorP3THDP13select_resultPP18Server_side_cursor+0x18c)[0x782aec]
/usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x370)[0x587520]
/usr/sbin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x64)[0x589d84]
/usr/sbin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x1b0)[0x58a3a0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xcaf)[0x57c38f]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57cf54]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2a5)[0x614d05]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x614e04]
/lib64/libpthread.so.0[0x39fec06367]
/lib64/libc.so.6(clone+0x6d)[0x39fe4d2f7d]

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

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.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the MySQL service cannot be effectively started or maintained in a stable state while the prepared statements continue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms