| Bug #108341 | MYSQL80 crashes | ||
|---|---|---|---|
| Submitted: | 30 Aug 2022 20:51 | Modified: | 3 Dec 2022 6:21 |
| Reporter: | Terry McDaniel | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Connection Handling | Severity: | S1 (Critical) |
| Version: | 8.0.30, 8.0.31 | OS: | Windows (microsoft windows server 2019 standard on vmware) |
| Assigned to: | CPU Architecture: | Any (intel(R) XEON(R) CPU E5-2698 v3 @ 2.30GHz) | |
[30 Aug 2022 20:51]
Terry McDaniel
[13 Oct 2022 9:32]
MySQL Verification Team
I verified that on Windows 8.0.30 is far too unstable. Crashing often in jemalloc.dll.. 2022-10-13T09:23:24.273299Z 0 [Warning] [MY-011302] [Server] Plugin mysqlx reported: 'Failed at SSL configuration: "SSL context is not usable without certificate and private key"' 2022-10-13T09:23:24.276284Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060 2022-10-13T09:23:24.276580Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: '8.0.30-commercial' socket: '' port: 3306 MySQL Enterprise Server - Commercial. 09:23:37 UTC - mysqld got exception 0xc0000005 ; 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... 7ffcc02bb496 jemalloc.dll!??? 7ffcc02bb918 jemalloc.dll!??? 7ffcc02bef91 jemalloc.dll!je_realloc() 7ffcc60e7ddd libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc612bcd2 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc612e7e3 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc60f956d libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc600263c libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc61a92ff libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffce8569a1d ntdll.dll!RtlActivateActivationContextUnsafeFast() 7ffce85675b6 ntdll.dll!LdrShutdownThread() 7ffce85a467e ntdll.dll!RtlExitUserThread() 7ffce5ce7eaa KERNELBASE.dll!FreeLibraryAndExitThread() 7ffce61d1cc4 ucrtbase.dll!_configthreadlocale() 7ffce6224759 ucrtbase.dll!_endthreadex() 7ff6228a4605 mysqld.exe!?modify_thread_cache_size@Per_thread_connection_handler@@SAXK@Z() 7ff623d78799 mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z() 7ff62393138c mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z() 7ffce61d1bb2 ucrtbase.dll!_configthreadlocale() 7ffce6807034 KERNEL32.DLL!BaseThreadInitThunk() 7ffce85a26a1 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.
[13 Oct 2022 9:33]
MySQL Verification Team
Obviously this is Windows specific bug. Simple had a table with two columns and ran mysqlslap: mysqlslap --create-schema=test -uroot --concurrency=50 --number-of-queries=100 --iterations=10000 --query="replace into t values(floor(rand()*100000),rand());"
[13 Oct 2022 9:42]
MySQL Verification Team
8.0.31 has same problem. Don't even need table to exist, seems just make rapid connections to server! 2022-10-13T09:41:32.597264Z 0 [System] [MY-010931] [Server] C:\ade\mysql-commercial-8.0.31-winx64\bin\mysqld.exe: ready for connections. 2022-10-13T09:41:36Z UTC - mysqld got exception 0xc0000005 ; 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... 7ffcc02bb496 jemalloc.dll!??? 7ffcc02bb918 jemalloc.dll!??? 7ffcc02bef91 jemalloc.dll!je_realloc() 7ffcc60e6cdd libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc612abd2 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc612d6e3 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc60f846d libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc60012ec libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffcc61a827f libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffce8569a1d ntdll.dll!RtlActivateActivationContextUnsafeFast() 7ffce85675b6 ntdll.dll!LdrShutdownThread() 7ffce85a467e ntdll.dll!RtlExitUserThread() 7ffce5ce7eaa KERNELBASE.dll!FreeLibraryAndExitThread() 7ffce61d1cc4 ucrtbase.dll!_configthreadlocale() 7ffce6224759 ucrtbase.dll!_endthreadex() 7ff7e7709245 mysqld.exe!handle_connection()[connection_handler_per_thread.cc:348] 7ff7e8d95b79 mysqld.exe!pfs_spawn_thread()[pfs.cc:2989] 7ff7e87905ac mysqld.exe!win_thread_start()[my_thread.cc:74] 7ffce61d1bb2 ucrtbase.dll!_configthreadlocale() 7ffce6807034 KERNEL32.DLL!BaseThreadInitThunk() 7ffce85a26a1 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.
[13 Oct 2022 15:31]
Bo Phommasa
I am experiencing the same issue. MySQL 8.0.29 on Windows Server 2019 2:50:02 UTC - mysqld got exception 0xc0000005 ; 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... 7fff6779b496 jemalloc.dll!??? 7fff6779b918 jemalloc.dll!??? 7fff6779ef91 jemalloc.dll!je_realloc() 7fff67cd7dbd libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff67d1bd02 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff67d1e813 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff67ce957d libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff67bf263c libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff67d9932f libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7fff83d05d37 ntdll.dll!RtlAnsiStringToUnicodeString() 7fff83d033f4 ntdll.dll!LdrShutdownThread() 7fff83d3a35e ntdll.dll!RtlExitUserThread() 7fff7fe9a33a KERNELBASE.dll!FreeLibraryAndExitThread() 7fff80e32794 ucrtbase.dll!_o_exp() 7fff80e80809 ucrtbase.dll!_endthreadex() 7ff644381885 mysqld.exe!?modify_thread_cache_size@Per_thread_connection_handler@@SAXK@Z() 7ff64581b519 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff6453f7fdc mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z() 7fff80e3268a ucrtbase.dll!_o_exp() 7fff83c07974 KERNEL32.DLL!BaseThreadInitThunk() 7fff83d3a2f1 ntdll.dll!RtlUserThreadStart()
[8 Nov 2022 16:10]
MySQL Verification Team
https://bugs.mysql.com/bug.php?id=108985 is a duplicate of this.
[8 Nov 2022 16:11]
MySQL Verification Team
https://bugs.mysql.com/bug.php?id=108924 is a duplicate of this.
[17 Nov 2022 13:03]
Jon Stephens
Documented fix as follows in the MySQL 8.0.32 changelog:
When compiling MySQL on Windows, the CMake
-DWITH_WIN_JEMALLOC option was not always handled
correctly.
Closed.
[7 Dec 2022 5:38]
MySQL Verification Team
A workaround for this bug in affected versions is to simply rename the jemalloc.dll so that it doesn't get loaded by mysqld.
