MySQL Bugs: #110231: mysqld crash windows with faulting module jemalloc.dll

Bug #110231	mysqld crash windows with faulting module jemalloc.dll
Submitted:	28 Feb 2023 10:33	Modified:	28 Feb 2023 15:34
Reporter:	Nicklas Holmgren	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S3 (Non-critical)
Version:	8.0.31.0	OS:	Windows (64bit Server 2022 Standard)
Assigned to:		CPU Architecture:	x86 (Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz)
Tags:	crash, jemalloc, mysqld

Description:
Event viewer revealed an error 2023-02-28 10:33:05:
Faulting application name: mysqld.exe, version: 8.0.31.0, time stamp: 0x6320bd31
Faulting module name: jemalloc.dll, version: 0.0.0.0, time stamp: 0x61b0a54c
Exception code: 0xc0000005
Fault offset: 0x000000000001b496
Faulting process id: 0xed0
Faulting application start time: 0x01d93e371c14b9d0
Faulting application path: C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe
Faulting module path: C:\Program Files\MySQL\MySQL Server 8.0\bin\jemalloc.dll
Report Id: 7946815f-324a-46c7-b603-23476253db71
Faulting package full name: 
Faulting package-relative application ID: 

Event viewer then gave an information log 2023-02-28 10:33:10:
Fault bucket 1376397232096206654, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: mysqld.exe
P2: 8.0.31.0
P3: 6320bd31
P4: jemalloc.dll
P5: 0.0.0.0
P6: 61b0a54c
P7: c0000005
P8: 000000000001b496
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e8c21a4-eb83-4371-be1f-68b433b3f9cf.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.27f9e4c8-73aa-4109-82cb-2edbd0333d8a.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f4095bf7-4fbe-4654-b033-9326ba07cfce.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.84d96bf6-8ae6-487f-95f6-65d30811bcf2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.29057a71-0f88-4cb7-be38-e991affb91b7.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mysqld.exe_51e132231ada1a25d11713c5f117a5f2ca675777_2d6a503a_10a73327-80b0-4db3-bb64-540291b0e839

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7946815f-324a-46c7-b603-23476253db71
Report Status: 268435456
Hashed bucket: 6bdbdc3cce0cbc608319f1fd78ecdf3e
Cab Guid: 0

Memory usage of this server is around 63% (5.1GB / 8GB).
Page file has been set to automatic which currently shows: minimum allkowed 16mb, recommended 1919MB, currently allocated 2176MB. The C disk has 72GB free, the database disk has 21.8GB free.

Has this bug been fixed in 8.0.32.0 ?

How to repeat:
No clue, this happened out of the blue.

Suggested fix:
No clue, since I'm running production community I'm not getting error on line bla bla bla in something.c . But if I was running a debug variant it should've shown me exactly what was wrong.

AppCrash log

Attachment: Report.wer (application/octet-stream, text), 11.96 KiB.

I read on change log for 8.0.32.0:
"Microsoft Windows: When compiling MySQL on Windows platforms, the CMake -DWITH_WIN_JEMALLOC option was not always handled correctly. (Bug #108341, Bug #34698376)"

Maybe this is fixed in next version? Does anyone who works on mysql code know?

Hi Mr. Holmgren,

Thank you very much, but this bug is fixed in 8.0.32, as per the Changelog entry.

If you continue to have problems with jemalloc.dll, then stop MySQL service, rename jemalloc.dll into some other .dll and try again.

But, please, first try 8.0.32.

Not a bug.

However,

This is a problem that is solved in 8.0.32.

We are upgrading to 8.0.32 in a couple of hours. If this is fixed in next version of MySQL. Then this issue can be closed.