MySQL Bugs: #53092: MySQL crashed when the load is pretty low

Bug #53092	MySQL crashed when the load is pretty low
Submitted:	23 Apr 2010 1:33	Modified:	22 Dec 2010 7:34
Reporter:	Jingqi Xu	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.1.41	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
MySQL 5.1.41 + InnoDB Plugin 1.0.6

gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)
./configure  '--prefix=/usr/local/mysql' '--with-mysqld-ldflags=-all-static' '--with-plugins=innobase' '--with-mysqld-user=mysql' '--with-charset=cp932' '--with-pthread' 'CFLAGS=-O3' 'CXXFLAGS=-O3' 'CXX=gcc'

######################
# Error Log
######################
100423  4:24:20 - 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=629145600
read_buffer_size=2097152
max_used_connections=47
max_threads=8000
threads_connected=21
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 33463650 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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 = (nil) thread_stack 0x40000
/usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x2e)[0x84210e]
/usr/local/mysql/libexec/mysqld(handle_segfault+0x322)[0x587d42]
/lib64/libpthread.so.0[0x3f9620e4c0]
/lib64/libc.so.6(memcpy+0xd2)[0x3f9567b512]
/usr/local/mysql/libexec/mysqld(_ZN6String6appendEPKcj+0x16d)[0x5854ad]
/usr/local/mysql/libexec/mysqld(thd_security_context+0x1a3)[0x5773d3]
/usr/local/mysql/libexec/mysqld[0x707bdd]
/usr/local/mysql/libexec/mysqld[0x72139f]
/usr/local/mysql/libexec/mysqld[0x76df72]
/usr/local/mysql/libexec/mysqld[0x76e78a]
/lib64/libpthread.so.0[0x3f96206367]
/lib64/libc.so.6(clone+0x6d)[0x3f956d30ad]
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.

How to repeat:
don't know

Suggested fix:
don't know

[root@s-slave1 mysql]# nm -n libexec/mysqld > /tmp/mysqld.sym
[root@s-slave1 mysql]# resolve_stack_dump -s /tmp/mysqld.sym -n /root/a
0x84210e my_print_stacktrace + 46
0x587d42 handle_segfault + 802
0x3f9620e4c0 _end + -1789106152
0x3f9567b512 _end + -1801242518
0x5854ad _ZN6String6appendEPKcj + 365
0x5773d3 thd_security_context + 419
0x707bdd innobase_mysql_print_thd + 29
0x72139f lock_print_info_all_transactions + 447
0x76df72 srv_printf_innodb_monitor + 402
0x76e78a srv_lock_timeout_and_monitor_thread + 890
0x3f96206367 _end + -1789139265
0x3f956d30ad _end + -1800883195

Related to http://bugs.mysql.com/bug.php?id=38883 ?

Please, check if this happens with version 5.1.45, where bug #38883 should be fixed.

"Changes in MySQL 5.1.42" describes that Bug#38883 was fixed in that version.
Can I check it with version 5.1.42 ?

I see pushes to 5.1.45 in the bug report, so I'd check with 5.1.45.

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".

Duplicated Bug#38883.