Bug #96610 InnoDB: Assertion failure in thread 140012361598720 in file rem0rec.cc line 578
Submitted: 22 Aug 2019 0:49 Modified: 23 Aug 2019 8:11
Reporter: Michael Finch Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.43 OS:CentOS (3.10.0-957.12.2.el7.x86_64)
Assigned to: MySQL Verification Team CPU Architecture:x86
Tags: multi_range_read

[22 Aug 2019 0:49] Michael Finch
We've seen multiple MySQL crashes on this database with the following error:

2019-08-20 22:57:59 7f572b13c700  InnoDB: Assertion failure in thread 140012361598720 in file rem0rec.cc line 578
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.
22:57:59 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.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

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

Thread pointer: 0x30b5c50
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 = 7f572b13bd40 thread_stack 0x40000

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

How to repeat:
Not sure.
[23 Aug 2019 8:11] MySQL Verification Team

This is a crash of a non-Oracle MySQL binary. If you cannot produce a reproducible test case that we can use to reproduce the bug on Oracle MySQL binary there's not much we can do to help.