Bug #86198 InnoDB: Assertion failure in thread 43144 in file ut0ut.cc line 931
Submitted: 5 May 2017 17:53 Modified: 7 Jun 2017 15:21
Reporter: Richard Fernandez Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.18 OS:Windows (Windows 2008 R2)
Assigned to: CPU Architecture:Any
Tags: assert

[5 May 2017 17:53] Richard Fernandez
Description:
This morning, mysqld crashed with the following output. I just did the upgrade from 5.5.36 to 5.6.36 to 5.7.18 this week and I have not had a crash of mysqld on version 5.536 for 2 years. I see that there may be some configuration issues I have with the new my.ini so I have included that also below.

2017-05-05 06:05:59 0xa888  InnoDB: Assertion failure in thread 43144 in file ut0ut.cc line 931
InnoDB: Failing assertion: !m_fatal
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2017-05-05T12:06:00.024873Z 444591 [Note] Aborted connection 444591 to db: 'bitnami_testlink' user: 'mrautomation' host: '10.65.210.112' (Got an error reading communication packets)
12:06:00 UTC - mysqld got exception 0x80000003 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=262144
max_used_connections=95
max_threads=10000
thread_count=27
connection_count=27
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3583419 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xef6bd890
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...
918520    
7545764e    
a1107a    
953ecb    
a323c7    
a2ff8c    
a23e19    
a237eb    
a66548    
aff20e    
afec81    
b009ac    
b00d9b    
afda1c    
b024c9    
a7f25f    
96bf9f    
32855e    
4ead05    
4e8d16    
4e7f96    
3511f8    
3539f5    
34d120    
34de14    
31eae6    
ba44d1    
9183d7    
753dc01d    
753dc001    
760a337a    
77e292b2    
77e29285    

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.

How to repeat:
Just using the my.ini file with MySQL version 5.7.18 under XAMPP with TestLink as the application.
[7 May 2017 15:21] MySQL Verification Team
Thank you for the bug report. Please describe here what were the steps you did to upgrade from 5.5 to 5.7.18. Thanks.
[8 Jun 2017 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".