[MDEV-24104] Server crashes with optimize_keyuse Created: 2020-11-03  Updated: 2023-06-09  Resolved: 2023-06-09

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

Type: Bug Priority: Major
Reporter: Allen Lee (Inactive) Assignee: Allen Lee (Inactive)
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Windows Server



 Description   

Server crashed with following stacktrace:

201102  8:30:02 [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.3.24-MariaDB-log
key_buffer_size=268435456
read_buffer_size=8388608
max_used_connections=77
max_threads=65537
thread_count=30
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 298047 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x21e30d44018
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!optimize_keyuse()[sql_select.cc:6569]
mysqld.exe!make_join_statistics()[sql_select.cc:5151]
mysqld.exe!JOIN::optimize_inner()[sql_select.cc:1952]
mysqld.exe!JOIN::optimize()[sql_select.cc:1499]
mysqld.exe!st_select_lex::optimize_unflattened_subqueries()[sql_lex.cc:4091]
mysqld.exe!JOIN::optimize_stage2()[sql_select.cc:2501]
mysqld.exe!JOIN::optimize_inner()[sql_select.cc:1977]
mysqld.exe!JOIN::optimize()[sql_select.cc:1499]
mysqld.exe!mysql_select()[sql_select.cc:4301]
mysqld.exe!handle_select()[sql_select.cc:370]
mysqld.exe!mysql_execute_command()[sql_parse.cc:4569]
mysqld.exe!sp_instr_stmt::exec_core()[sp_head.cc:3704]
mysqld.exe!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:3434]
mysqld.exe!sp_instr_stmt::execute()[sp_head.cc:3608]
mysqld.exe!sp_head::execute()[sp_head.cc:1377]
mysqld.exe!sp_head::execute_procedure()[sp_head.cc:2404]
mysqld.exe!do_execute_sp()[sql_parse.cc:2983]
mysqld.exe!Sql_cmd_call::execute()[sql_parse.cc:3223]
mysqld.exe!mysql_execute_command()[sql_parse.cc:6032]
mysqld.exe!mysql_parse()[sql_parse.cc:7814]
mysqld.exe!dispatch_command()[sql_parse.cc:1850]
mysqld.exe!do_command()[sql_parse.cc:1393]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:358]
mysqld.exe!tp_callback()[threadpool_common.cc:185]
ntdll.dll!RtlInitializeCriticalSection()
ntdll.dll!RtlReleaseSRWLockExclusive()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.



 Comments   
Comment by Elena Stepanova [ 2023-06-09 ]

Adjusting the resolution, a genuine server crash can hardly be "Won't fix"

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