Bug #77914 mysql crash InnoDB: Assertion failure
Submitted: 3 Aug 2015 9:35 Modified: 4 Aug 2015 4:14
Reporter: Dmitriy Krasnikov Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Memcached Severity:S2 (Serious)
Version:5.6.26 OS:Red Hat (6.6)
Assigned to: CPU Architecture:Any

[3 Aug 2015 9:35] Dmitriy Krasnikov
After upgrade to 5.6.26 have every 2 days mysql crashes.
ON error log write next:

2015-07-31 7f76c21fc700  InnoDB: Assertion failure in thread 140148039730944 in file rem0rec.cc line 577
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.
23:17:52 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 = 1842169 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f74687da710
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 = 7f76c21fb138 thread_stack 0x40000

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

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.
150731 mysqld_safe Number of processes running now: 0
150731 mysqld_safe mysqld restarted
2015-07-31  0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

How to repeat:
[3 Aug 2015 9:47] MySQL Verification Team
Hello Dmitriy,

Please do not submit the same bug more than once. An existing bug report Bug #74222 already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

[3 Aug 2015 17:07] Dmitriy Krasnikov
I add more information(Hide mode) to bug http://bugs.mysql.com/bug.php?id=74222 , but i no have options to change status back to Open.
[17 Nov 2016 23:32] A Rahut
For some reason I am not able to access the notes on the linked bug 

Any ideas why?