Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
10.5.4, 10.5.5
-
Windows Server 2019
Description
Faulting application name: mysqld.exe, version: 10.5.4.0, time stamp: 0x5ef224e3
Faulting module name: server.dll, version: 10.5.4.0, time stamp: 0x5ef224cc
Exception code: 0xc0000409
Fault offset: 0x0000000000734ec4
Faulting process id: 0x14c4
Faulting application start time: 0x01d67067051ef86e
Faulting application path: C:\Program Files\MariaDB 10.5\bin\mysqld.exe
Faulting module path: C:\Program Files\MariaDB 10.5\bin\server.dll
Report Id: 5631281e-f60e-4dcc-b31b-2b9fe8ab9205
Faulting package full name:
Faulting package-relative application ID:
200812 5:05:46 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.5.4-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=43
max_threads=65537
thread_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136407 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x29f33d6fb38
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...
server.dll!row_sel_copy_cached_fields_for_mysql()[row0sel.cc:3640]
server.dll!row_search_mvcc()[row0sel.cc:4292]
server.dll!ha_innobase::general_fetch()[ha_innodb.cc:9227]
server.dll!handler::ha_rnd_next()[handler.cc:3037]
server.dll!rr_sequential()[records.cc:511]
server.dll!sub_select()[sql_select.cc:20619]
server.dll!do_select()[sql_select.cc:20134]
server.dll!JOIN::exec_inner()[sql_select.cc:4444]
server.dll!JOIN::exec()[sql_select.cc:4226]
server.dll!mysql_select()[sql_select.cc:4651]
server.dll!handle_select()[sql_select.cc:417]
server.dll!execute_sqlcom_select()[sql_parse.cc:6209]
server.dll!mysql_execute_command()[sql_parse.cc:3939]
server.dll!mysql_parse()[sql_parse.cc:7997]
server.dll!dispatch_command()[sql_parse.cc:1877]
server.dll!do_command()[sql_parse.cc:1355]
server.dll!threadpool_process_request()[threadpool_common.cc:354]
server.dll!tp_callback()[threadpool_common.cc:194]
ntdll.dll!RtlInitializeCriticalSection()
ntdll.dll!RtlReleaseSRWLockExclusive()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x29f33cd90d0): SELECT * FROM storages WHERE Type='group' AND Type_ID='710'
Connection ID (thread ID): 752
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
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.
Writing a core file at C:\Program Files\MariaDB 10.5\data
InnoDB: using atomic writes.