Bug #81560 mysqld crashed
Submitted: 24 May 2016 7:13 Modified: 28 Jun 2016 11:45
Reporter: bee robert Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6.26 MySQL Enterprise Server - Advance OS:SUSE (suse linux 11 sp3)
Assigned to: CPU Architecture:Any

[24 May 2016 7:13] bee robert
error logs info:

2016-05-13 12:16:08 7f3235d24700  InnoDB: Assertion failure in thread 139853628065536 in file srv0srv.cc line 1750
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
04:16:08 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.

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

Thread pointer: 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 = 0 thread_stack 0x40000
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.
160513 12:16:08 mysqld_safe Number of processes running now: 0
160513 12:16:08 mysqld_safe mysqld restarted

if more logs or info needed, pls send to my email: bigang@huawei.com

How to repeat:

Suggested fix:
solution or patch.
[28 Jun 2016 11:45] MySQL Verification Team
Hello Robert,

Thank you for the report.
Do you have a repeatable test case to trigger this issue?  If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.