MySQL Bugs: #111961: MySQL 8.0.34 crashing suddenly

Bug #111961	MySQL 8.0.34 crashing suddenly
Submitted:	3 Aug 2023 18:21	Modified:	3 Aug 2023 18:32
Reporter:	Tuhinanshu Mr	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	8.0.34	OS:	Windows (Windows Server 2019)
Assigned to:		CPU Architecture:	Other (x64)

Description:
Today, MySQL was stopped abruptly with below error log. I am not able to make much out of it. Request team's help in identifying what could be causing this and how to resolve it.

2023-08-03T08:16:08Z UTC - mysqld got exception 0xc0000005 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x2c2a0619070
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...
7ffde7e513b6    VCRUNTIME140.dll!memcpy()
7ff6c80bd5b7    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff6c80bcbda    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff6c6a26563    mysqld.exe!?ha_rnd_next@handler@@QEAAHPEAE@Z()
7ff6c6e188ad    mysqld.exe!?create_ondisk_from_heap@@YA_NPEAVTHD@@PEAUTABLE@@H_N2PEA_N@Z()
7ff6c6f44bb1    mysqld.exe!?MaterializeQueryBlock@?$MaterializeIterator@VDummyIteratorProfiler@@@@AEAA_NAEBUQueryBlock@materialize_iterator@@PEA_K@Z()
7ff6c6f43236    mysqld.exe!?Init@?$MaterializeIterator@VDummyIteratorProfiler@@@@UEAA_NXZ()
7ff6c6dc75d8    mysqld.exe!?ExecuteIteratorQuery@Query_expression@@QEAA_NPEAVTHD@@@Z()
7ff6c6dc8b33    mysqld.exe!?execute@Query_expression@@QEAA_NPEAVTHD@@@Z()
7ff6c6cfaafe    mysqld.exe!?execute_inner@Sql_cmd_dml@@MEAA_NPEAVTHD@@@Z()
7ff6c6cfa982    mysqld.exe!?execute@Sql_cmd_dml@@UEAA_NPEAVTHD@@@Z()
7ff6c6bf561a    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff6c6bf03ef    mysqld.exe!?dispatch_sql_command@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff6c6beefec    mysqld.exe!?dispatch_command@@YA_NPEAVTHD@@PEBTCOM_DATA@@W4enum_server_command@@@Z()
7ff6c6bf07a6    mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
7ff6c6a1b458    mysqld.exe!?thread_id@THD@@QEBAIXZ()
7ff6c8037029    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff6c7ab3a8c    mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7ffdf49d03ba    ucrtbase.dll!_o_exp()
7ffdf5587e94    KERNEL32.DLL!BaseThreadInitThunk()
7ffdf7917ad1    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2c23819dd10): select pm.Package_AWB, pm.PACKAGE_OID, pm.PACKAGE_DC,pm.PACKAGE_LENGTH,  pm.PACKAGE_WIDTH , pm.PACKAGE_HEIGHT , pm.PACKAGE_WEIGHT, pm.PRIMARY_SORT_BAY_ID, pm.SECONDARY_SORT_PTL_ID, pm.UPLOADED_TIMESTAMP,pm.INSCANNED_TIMESTAMP,pm.PRIMARY_SORTED_TIMESTAMP,pm.IN_BAG_TIMESTAMP,pm.MANIFESTED_TIMESTAMP, pm.BAG_CLOSED_TIMESTAMP,bm.Bay_Operator_Name,bom.Bay_Operator_Name, pm.Delhivery_Bag_Id, pm.Inscan_Mode, pm.Inducted_Lane, pm.Recirculation_Count from Package_Master pm left join Bay_Operator bm on bm.Bay_Operator_EmployeeId= pm.Put_bag_User  left join Bay_Operator bom on bom.Bay_Operator_Employeeid= pm.Close_Bag_User where (ifnull(pm.In_Bag_Timestamp,0) != 0 and Unix_Timestamp(pm.In_Bag_Timestamp) !=0) and pm.In_Bag_Timestamp >= timestamp('2023-07-20 07:00:00') and pm.In_Bag_Timestamp < timestamp('2023-08-03 14:00:00') union select pa.Package_AWB, pa.PACKAGE_OID, pa.PACKAGE_DC, pa.PACKAGE_LENGTH,  pa.PACKAGE_WIDTH , pa.PACKAGE_HEIGHT , pa.PACKAGE_WEIGHT, pa.PRIMARY_SORT_BAY_ID, pa.SECONDARY_SORT_PTL_ID, pa.UPLOADED
Connection ID (thread ID): 13742512
Status: NOT_KILLED

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.

How to repeat:
N/A

configuration file for reference

Attachment: my.ini (application/octet-stream, text), 14.67 KiB.

Hi Mr. Mr, Tuhinanshu,

Thank you for your bug report. However ......

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, such that we are able to repeat the problem, we can then proceed to process this report.

We have also noticed that your my.ini configuration file is designed for a computer with terabyte of RAM.

Please, also read our Reference Manual, on the server variables that you have set in your my.ini.

Thank you for your interest in MySQL.