Bug #113831 mysql crashes ramdonally during backup
Submitted: 31 Jan 11:28 Modified: 31 Jan 13:17
Reporter: Manuele Faustini Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:8.0.35 OS:Windows (windows server 2016)
Assigned to: CPU Architecture:Any

[31 Jan 11:28] Manuele Faustini
Description:
Hi community

mysql server crashes randomly when mysqldump is executed.

mysqld got exception 0xc0000005 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x1b811c17070
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...
7ff7f3bcc51e    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3bcb6eb    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3bcb644    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3c82629    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3c81bf1    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3c75986    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3c747c5    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f3b0efcc    mysqld.exe!?do_reset@Zstd_dec@compression@transaction@binary_log@@EEAAXXZ()
7ff7f29f890a    mysqld.exe!?ha_open@handler@@QEAAHPEAUTABLE@@PEBDHHPEBVTable@dd@@@Z()
7ff7f2a7a4ad    mysqld.exe!?open_table_from_share@@YAHPEAVTHD@@PEAUTABLE_SHARE@@PEBDIIIPEAUTABLE@@_NPEBVTable@dd@@@Z()
7ff7f2bb427b    mysqld.exe!?open_table@@YA_NPEAVTHD@@PEAVTable_ref@@PEAVOpen_table_context@@@Z()
7ff7f2bb2c47    mysqld.exe!?open_and_lock_tables@@YA_NPEAVTHD@@PEAVTable_ref@@IPEAVPrelocking_strategy@@@Z()
7ff7f2bb52f5    mysqld.exe!?open_tables@@YA_NPEAVTHD@@PEAPEAVTable_ref@@PEAIIPEAVPrelocking_strategy@@@Z()
7ff7f2be41be    mysqld.exe!?killall_non_super_threads@@YAXPEAVTHD@@@Z()
7ff7f2be61d6    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff7f2be25ff    mysqld.exe!?dispatch_sql_command@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff7f2be11fa    mysqld.exe!?dispatch_command@@YA_NPEAVTHD@@PEBTCOM_DATA@@W4enum_server_command@@@Z()
7ff7f2be29b6    mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
7ff7f29e9b28    mysqld.exe!?thread_id@THD@@QEBAIXZ()
7ff7f403cff9    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff7f3aaac0c    mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7ffefbd2fb80    ucrtbase.dll!_o__realloc_base()
7ffefc6684d4    KERNEL32.DLL!BaseThreadInitThunk()
7ffefefb1791    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1bbed930030): LOCK TABLES `anodedyeexam` READ /*!32311 LOCAL */,`anodempidefect` READ /*!32311 LOCAL */,`anodempiexam` READ /*!32311 LOCAL */,`anodepassaudit` READ /*!32311 LOCAL */,`anodeultraexam` READ /*!32311 LOCAL */,`anodeweld` READ /*!32311 LOCAL */,`anodeweldaudit` READ /*!32311 LOCAL */,`applus` READ /*!32311 LOCAL */,`area` READ /*!32311 LOCAL */,`asbuild_comment` READ /*!32311 LOCAL */,`aslaid` READ /*!32311 LOCAL */,`aslaid_hilo_measurement` READ /*!32311 LOCAL */,`aslaidcoataudit` READ /*!32311 LOCAL */,`aslaidcoatbatch` READ /*!32311 LOCAL */,`aslaidfieldcoat` READ /*!32311 LOCAL */,`aslaidheatexam` READ /*!32311 LOCAL */,`aslaidrootexam` READ /*!32311 LOCAL */,`assessment` READ /*!32311 LOCAL */,`attach` READ /*!32311 LOCAL */,`autdefect` READ /*!32311 LOCAL */,`autexam` READ /*!32311 LOCAL */,`auttech` READ /*!32311 LOCAL */,`batch` READ /*!32311 LOCAL */,`batchtype` READ /*!32311 LOCAL */,`brazers` READ /*!32311 LOCAL */,`clean` READ /*!32311 LOCAL */,`coataudit` READ /*!32311 LOCAL */,`coatbatch` READ /*!
Connection ID (thread ID): 17087
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:
run many mysqldump commands consecutively
[31 Jan 13:17] MySQL Verification Team
Hi Mr. Faustini,

Thank you very much for your bug report.

However, you have not sent us a fully repeatable test case.

What we need is the exact and ONLY ONE mysqldump command, that you used,  and we need the EXACT table , with it's contents on which mysqldump crashes the server.

When you send us a repeatable test case, we shall be happy to proceed with it's processing ......

Can't repeat.