[MDEV-26895] MariaDB crashes with "SHOW FULL PROCESSLIST" command. Created: 2021-10-25  Updated: 2021-12-06  Resolved: 2021-12-06

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.27
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Nilnandan Joshi Assignee: Unassigned
Resolution: Incomplete Votes: 1
Labels: need_feedback


 Description   

MariaDB crashes with "SHOW FULL PROCESSLIST" command intermittently. (about one or two times in a month)

211022 11:00:36 [ERROR] mysqld got exception 0xc0000005 ;
....
Server version: 10.3.27-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=70
max_threads=65537
thread_count=58
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137167 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x2099429dff8
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...
mysqld.exe!?mysqld_list_processes@@YAXPEAVTHD@@PEBD_N@Z()
mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@@Z()
mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEADIPEAVParser_state@@_N3@Z()
mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI_N3@Z()
mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
mysqld.exe!?pool_of_threads_scheduler@@YAXPEAUscheduler_functions@@PEAKPEAI@Z()
mysqld.exe!?tp_callback@@YAXPEAUTP_connection@@@Z()
ntdll.dll!RtlInitializeCriticalSection()
ntdll.dll!RtlAcquireSRWLockExclusive()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2098f4fb510): SHOW FULL PROCESSLIST
Connection ID (thread ID): 2517892
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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on

I found one old bug but not sure if it's related to this.
MDEV-12951
(fixed in 10.2.9)



 Comments   
Comment by Nilnandan Joshi [ 2021-10-26 ]

Hi julien.fritsch, unfortunately, we don't have test case to reproduce as customer faces this issue once or twice in a month. There is no any pattern. As it is windows OS, can we ask any other details from customer ?

Generated at Thu Feb 08 09:48:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.