Bug #91569 InnoDB: Assertion failure in thread 140065796044544 in file btr0pcur.cc line 430

• Submitted: 9 Jul 2018 4:34
• Modified: 13 Aug 2018 12:07
• Reporter: Manoj K
• Status: Closed
• Category: MySQL Server: InnoDB storage engine
• Severity: S3 (Non-critical)
• Version: mysql-community-server-5.6.40-1debian9
• OS: Debian (stretch)
• CPU Architecture: x86 (any)
• Tags: InnoDB: Assertion failure

[9 Jul 2018 4:34] Manoj K

Description:
Unable to take mysqldump from database. While taking dump mysql service getting restarted by throwing below error, 

2018-07-09 04:19:35 7f639c04b700  InnoDB: Assertion failure in thread 140065796044544 in file btr0pcur.cc line 430
InnoDB: Failing assertion: page_is_comp(next_page) == page_is_comp(page)
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:19:35 UTC - mysqld got signal 6 ;
  

How to repeat:
no particular steps to repeat it, in blog saying that, issue has been fixed in 5.6.31 version, but unfortunately its still continues (https://bugs.mysql.com/bug.php?id=75304)

[12 Jul 2018 13:40] MySQL Verification Team

Hi,

Thank you very much for your report.

However, you are not using our latest 5.6 release, so we will wait that you repeat this assert with latest 5.6 release, or even better, with latest 5.7 release.

Thanks in advance.

[13 Aug 2018 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".