Bug #71566 MySQL 5.5.35 Segfault
Submitted: 3 Feb 2014 15:35 Modified: 24 Aug 2014 20:16
Reporter: Steven Johnson Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: Merge storage engine Severity:S2 (Serious)
Version:5.5.35 OS:Linux (RHEL 6.4)
Assigned to: CPU Architecture:Any

[3 Feb 2014 15:35] Steven Johnson
We have had several segfaults recently on a RHEL 6.4 server running MySQL 5.5.35. We have not found any existing bugs that show this issue or any fixes that address this issue in 5.5.36, as such we are raising this as a bug. 

See below for log output:

07:06:03 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5552003 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2db5100
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 = 7f1375becd98 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f12d8004bc0): is an invalid pointer
Connection ID (thread ID): 530286

How to repeat:
We are currently unaware of how to repeat this segfault.
[11 Mar 2014 12:38] Steven Johnson
We appear to have found the cause of the issue. 

The variable "table_open_cache" was erroneously set to a very small value. 

Setting this to the correct value appears to have mitigated the segfaults.
[24 Jul 2014 20:16] Sveta Smirnova
Thank you for the report.

Backtrace is not really useful unfortunately. Please try to find out what leads to segfault in your case and, at least, explain why you choose "Merge table engine" category for this bug. Do you use Merge tables when the issue happens?
[25 Aug 2014 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".