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: | |
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
[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.