MySQL Bugs: #95883: server crash very day

Bug #95883	server crash very day
Submitted:	19 Jun 2019 14:24	Modified:	22 Jul 2019 11:49
Reporter:	Coffee Mill	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:		OS:	Windows (windows server 2012r2)
Assigned to:		CPU Architecture:	Any

Description:
02:55:04 UTC - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=65536
max_used_connections=0
max_threads=1000
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338184 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
7ff6eba83ed0    mysqld.exe!?init@Rpl_info_values@@QEAA_NXZ()
7ff6ebe5eff3    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebe5eeb9    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebf3f352    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebf3f1b8    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebf21099    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebf214d8    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebecf942    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebecf134    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebecef3a    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebe2b90d    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebe2ac7e    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebe2aead    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebe2ac44    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebcf32d6    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6ebcf30ec    mysqld.exe!??1?$lock_guard@Vmutex@std@@@std@@QEAA@XZ()
7ff6eae70af5    mysqld.exe!?xa_trans_rolled_back@XID_STATE@@QEAA_NXZ()
7ff6eae35227    mysqld.exe!?plugin_foreach_with_mask@@YA_NPEAVTHD@@PEAP6A_N0PEAUst_plugin_int@@PEAX@ZHI2@Z()
7ff6eae34fb6    mysqld.exe!?plugin_foreach_with_mask@@YA_NPEAVTHD@@P6A_N0PEAUst_plugin_int@@PEAX@ZHI2@Z()
7ff6eae6dc54    mysqld.exe!?ha_recover@@YAHPEBV?$memroot_unordered_set@_KU?$hash@_K@std@@U?$equal_to@_K@2@@@@Z()
7ff6eb9b91cb    mysqld.exe!?binlog_query@THD@@QEAAHW4enum_binlog_query_type@1@PEBD_K_N33H@Z()
7ff6eb9c4496    mysqld.exe!?open_binlog@MYSQL_BIN_LOG@@QEAAHPEBD@Z()
7ff6eadd427d    mysqld.exe!?init_common_variables@@YAHXZ()
7ff6eaddb988    mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
7ff6eadd6eb5    mysqld.exe!?mysql_service@@YAHPEAX@Z()
7ff6eadd74ce    mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
7ff6ec10ebed    mysqld.exe!?my_casedn_ujis@@YA_KPEBUCHARSET_INFO@@PEAD_K12@Z()
7ffe181813d2    KERNEL32.DLL!BaseThreadInitThunk()
7ffe19c403c4    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.

How to repeat:
It happens every day.

Hi,

Thank you for your bug report.

However, I can not see how can we verify this as a repeatable bug report. First of all, we do not see what is the version and release of our server that you are using.

Second, this crash happens in the main thread, due to the rollback of the XA transaction. How many servers are involved in this XA transaction. What are the tables and DML's involved, so that we can try to repeat it. We need a fully repeatable test case, if we are to process this bug any further.

Last, but not least, you are using some plugin, but the stacktrace does not say what plugin are you exactly using.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".