Bug #106245 MySQL 8.0.28 crashing in a loop
Submitted: 22 Jan 2022 14:34 Modified: 22 Jan 2022 17:22
Reporter: Niall Finn Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.28 OS:Windows (Server 2016)
Assigned to: CPU Architecture:Any (x64)

[22 Jan 2022 14:34] Niall Finn
Description:
After installing version 8.0.28 (including a fresh install), server repeatedly crashes.

Sample error:

2022-01-22T13:39:24.686683Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-01-22T13:39:24.688757Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.28) starting as process 17848
2022-01-22T13:39:24.732268Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-01-22T13:39:28.167226Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-01-22T13:39:29.491045Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2022-01-22T13:39:29.497986Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2022-01-22T13:39:29.606700Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-01-22T13:39:29.607611Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-01-22T13:39:29.651818Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2022-01-22T13:39:29.652024Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: '8.0.28'  socket: ''  port: 3306  MySQL Community Server - GPL.
2022-01-22T13:41:11.625922Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-01-22T13:41:11.627329Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-01-22T13:41:11.740634Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-01-22T13:41:11.740657Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 18116
2022-01-22T13:41:11.742148Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:41:11 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
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...
7ff73f9bfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff73ebf004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff73ebefe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff73f9a643a    mysqld.exe!?my_abort@@YAXXZ()
7ff73fbdc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff73fb2bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff73fb2d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff73fb2c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff73fb4e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff73fb9e091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff73fb9b7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffab78efb80    ucrtbase.dll!_o__realloc_base()
7ffabace84d4    KERNEL32.dll!BaseThreadInitThunk()
7ffabade1791    ntdll.dll!RtlUserThreadStart()
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.
2022-01-22T13:41:11.881474Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 17720
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

How to repeat:
install using Windows msi
[22 Jan 2022 17:22] MySQL Verification Team
Thank you for the bug report. I couldn't repeat on 3 computers, this error could  be caused by hardware or OS problems.
[22 Feb 2022 9:23] Frantz ROCHARD
Same error on 3 computers (windows 10 - Windows 2016 - windows 2012)

I got this crash when i use SQL DUMP function of SQLyog (https://webyog.com/product/sqlyog/)  on large table. (work well before 8.0.28)

Hopefully, mysqldump command works, i can backup the base before downgrade

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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:50:11 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
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...
7ff6a0fbfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff6a01f004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff6a01efe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff6a0fa643a    mysqld.exe!?my_abort@@YAXXZ()
7ff6a11dc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff6a112bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a112d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a112c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a114e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff6a119e091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff6a119b7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffd968f1bb2    ucrtbase.dll!_configthreadlocale()
7ffd97d17034    KERNEL32.DLL!BaseThreadInitThunk()
7ffd99062651    ntdll.dll!RtlUserThreadStart()
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.
2022-02-22T08:50:11.683060Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 13720
2022-02-22T08:50:11.683070Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.