Bug #75889 *** glibc detected *** .../5.6.14/bin/mysqld: double free or corruption (!prev):
Submitted: 13 Feb 2015 9:27 Modified: 13 Mar 2015 10:13
Reporter: Ralf Vogel Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.14 OS:Linux (2.6.32-358.6.1.el6.x86_64)
Assigned to: CPU Architecture:Any

[13 Feb 2015 9:27] Ralf Vogel 
Description:
*** glibc detected *** /srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld: double free or corruption (!prev): 0x00007fa3b1ebad70 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3e1c676166]
/lib64/libc.so.6[0x3e1c678ca3]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(delete_queue+0x14)[0x8ff734]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition29destroy_record_priority_queueEv+0x22)[0xb317f2]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition9index_endEv+0x89)[0xb31899]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN13st_join_table7cleanupEv+0x195)[0x70ebf5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN7cleanupEb+0x127)[0x70ed47]
mysqladm@mucxv017> ^C
mysqladm@mucxv017> unaem -a
-sh: unaem: command not found
mysqladm@mucxv017> uname -a
Linux mucxv017 2.6.32-358.6.1.el6.x86_64 #1 SMP Fri Mar 29 16:51:51 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
mysqladm@mucxv017> cat zbxbuxdb.log
Fri Feb 13 00:05:04 CET 2015: logrotation happened.
*** glibc detected *** /srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld: double free or corruption (!prev): 0x00007fa3b1ebad70 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3e1c676166]
/lib64/libc.so.6[0x3e1c678ca3]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(delete_queue+0x14)[0x8ff734]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition29destroy_record_priority_queueEv+0x22)[0xb317f2]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition9index_endEv+0x89)[0xb31899]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN13st_join_table7cleanupEv+0x195)[0x70ebf5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN7cleanupEb+0x127)[0x70ed47]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN9join_freeEv+0x49)[0x70eef9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN4execEv+0x304)[0x6c9074]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld[0x70e9e9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xbc)[0x70fd0c]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x175)[0x70ff15]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld[0x6ea4c9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3575)[0x6ef6c5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x318)[0x6f30c8]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xbcb)[0x6f449b]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z10do_commandP3THD+0xd7)[0x6f6297]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x116)[0x6be416]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(handle_one_connection+0x45)[0x6be4f5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(pfs_spawn_thread+0x126)[0x979186]
/lib64/libpthread.so.0[0x3e1ce079d1]
/lib64/libc.so.6(clone+0x6d)[0x3e1c6e8b5d]
======= Memory map: ========

...

06:32:36 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=228
max_threads=600
thread_count=184
connection_count=183
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3165181 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x100ce8c0
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 = 7fa43e120e10 thread_stack 0x40000
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(my_print_stacktrace+0x35)[0x900985]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(handle_fatal_signal+0x3e8)[0x66e588]
/lib64/libpthread.so.0[0x3e1ce0f710]
/lib64/libc.so.6(gsignal+0x35)[0x3e1c632925]
/lib64/libc.so.6(abort+0x175)[0x3e1c634105]
/lib64/libc.so.6[0x3e1c670837]
/lib64/libc.so.6[0x3e1c676166]
/lib64/libc.so.6[0x3e1c678ca3]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(delete_queue+0x14)[0x8ff734]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition29destroy_record_priority_queueEv+0x22)[0xb317f2]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN12ha_partition9index_endEv+0x89)[0xb31899]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN13st_join_table7cleanupEv+0x195)[0x70ebf5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN7cleanupEb+0x127)[0x70ed47]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN9join_freeEv+0x49)[0x70eef9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_ZN4JOIN4execEv+0x304)[0x6c9074]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld[0x70e9e9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xbc)[0x70fd0c]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x175)[0x70ff15]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld[0x6ea4c9]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3575)[0x6ef6c5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x318)[0x6f30c8]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xbcb)[0x6f449b]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z10do_commandP3THD+0xd7)[0x6f6297]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x116)[0x6be416]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(handle_one_connection+0x45)[0x6be4f5]
/srv/mysqlsys/mysqladm/product/5.6.14/bin/mysqld(pfs_spawn_thread+0x126)[0x979186]
/lib64/libpthread.so.0[0x3e1ce079d1]
/lib64/libc.so.6(clone+0x6d)[0x3e1c6e8b5d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa3998cfc80): SELECT * FROM history_uint h WHERE h.itemid='55464' ORDER BY h.clock DESC LIMIT 1 OFFSET 0
Connection ID (thread ID): 15174071
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.
150213 07:32:38 mysqld_safe Number of processes running now: 0
150213 07:32:38 mysqld_safe mysqld restarted

How to repeat:
not known - occurred just one time
[13 Feb 2015 10:13] MySQL Verification Team 
Please test new version 5.6.23. Thanks.
[14 Mar 2015 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".