MySQL Bugs: #48965: Crash: frame pointer is NULL, did you compile with -fomit-frame-pointer?

Bug #48965	Crash: frame pointer is NULL, did you compile with -fomit-frame-pointer?
Submitted:	22 Nov 2009 0:55	Modified:	27 Jan 2010 9:56
Reporter:	Justin Keller	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S1 (Critical)
Version:	mysql Ver 14.12 Distrib 5.0.86, for red	OS:	Linux (CentOS release 5.4 (Final))
Assigned to:		CPU Architecture:	Any
Tags:	frame pointer is NULL, mysqld got signal 11

Description:
MySQL crashed recently; shut itself down. The following was outputted to the error_log. It has not crashed since, but I am a bit worried about it happening again and further downtime. The only real informative message in the error_log is: frame pointer is NULL.

Thanks for the help.

------

091113 16:35:12 mysqld started
091113 16:35:16 InnoDB: Started; log sequence number 0 162010813
091113 16:35:17 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.86-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
091119 20:24:35 - 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=67108864
read_buffer_size=1048576
max_used_connections=7
max_connections=25
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 142335 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
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.

Number of processes running now: 0
091119 20:24:36 mysqld restarted
091119 20:24:36 - 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.
091119 20:24:36 mysqld ended

How to repeat:
Unsure. Only happened once thus far, has not happened since.

Please, send your my.cnf file content and the result of

free
uname -a

Linux commands.

---------------------------------------------
my.cnf
---------------------------------------------
[mysqld]
skip-bdb
skip-ndbcluster
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
default-storage-engine=InnoDB
long_query_time=3
log-slow-queries=/var/log/mysql_slow.log
expire_logs_days=14
max_connections=25
external-locking

port=3306
net_retry_count=5
max_connect_errors=50
wait_timeout=3600
connect_timeout=15

open_files_limit=1536
key_buffer_size=64M
innodb_buffer_pool_size=128M
innodb_additional_mem_pool_size=8M
innodb_log_buffer_size=8M
group_concat_max_len=16k
max_sort_length=16k
max_length_for_sort_data=16k
query_cache_type=1
query_cache_limit=4M
query_cache_size=64M
innodb_thread_concurrency=16
thread_concurrency=16
thread_cache=128
thread_stack=1M
read_buffer_size=1M
join_buffer_size=2M
read_rnd_buffer_size=1M
table_cache=512
tmp_table_size=256M
max_heap_table_size=256M
innodb_log_file_size=128M
innodb_flush_log_at_trx_commit=1
innodb_file_per_table
log-warnings

user=mysql
old_passwords=1

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

---------------------------------------------
uname -a
---------------------------------------------
Linux db1.mydomainhere.com 2.6.31-302-rs #7 SMP Thu Oct 29 22:57:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux

---------------------------------------------
free -m
---------------------------------------------
             total       used       free     shared    buffers     cached
Mem:           321        276         45          0          4         99
-/+ buffers/cache:        171        149
Swap:          511          1        510

Looks like your my.cnf settings are too high for the small amount of RAM you have. With these global buffers:

key_buffer_size=64M
innodb_buffer_pool_size=128M
innodb_additional_mem_pool_size=8M
innodb_log_buffer_size=8M
query_cache_size=64M

your server uses 272M of memory for sure (if key buffer is used). Add these per-thread buffers to the picture:

thread_stack=1M
read_buffer_size=1M
join_buffer_size=2M
read_rnd_buffer_size=1M

and you'll see that each connection adds several megabytes more. And if any big enough temporary table is created in any connection, with these settings it can take a lot of memory:

tmp_table_size=256M
max_heap_table_size=256M

So, your crash can easily be related to out of memory condition. Please, decrease some of global buffers and set tmp_table_size and max_heap_table_size to 16M or so. Then check if crash will happen again.

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

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