Bug #94675 MySQL56 service shutsdown when a user connects through app
Submitted: 15 Mar 2019 13:02 Modified: 15 Apr 2019 14:43
Reporter: Benjamin Mwau Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:MySQL56 OS:Windows (server 2012 standard)
Assigned to: CPU Architecture:Other (INTEL XEON )
Tags: administrator@vitalray.com, bmwau@vitalray.com

[15 Mar 2019 13:02] Benjamin Mwau 
Description:
2019-03-15 15:21:52 510  InnoDB: Assertion failure in thread 1296 in file

When Start the application behind the MYSQL database and user tries to query app dat, MySQL56 service shuts down.  

How to repeat:
btr0cur.cc line 274
InnoDB: Failing assertion: btr_page_get_next(get_block->frame, mtr) == page_get_page_no(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.
Plugin 'FEDERATED' is disabled.
2019-03-15 15:22:40 1308 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
[15 Mar 2019 14:43] MySQL Verification Team 
Thank you for the bug report. Which exactly server version are you using 5.6.XX and check for data corruption also.
[16 Apr 2019 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".