[MDEV-33321] A crash on 10.11.6 reporting as the log directed. Created: 2024-01-28  Updated: 2024-01-30

Status: Needs Feedback
Project: MariaDB Server
Component/s: Optimizer, Storage Engine - InnoDB
Affects Version/s: 10.11.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Mitchell Lee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Windows 11



 Description   

The log copy here. I do not know why detail.

240128 19:20:08 [ERROR] mysqld got exception 0xc0000005 ;
Sorry, we probably made a mistake, and this is a bug.
 
Your assistance in bug reporting will enable us to fix this for the next release.
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.11.6-MariaDB-log source revision: fecd78b83785d5ae96f2c6ff340375be803cd299
key_buffer_size=16777216
read_buffer_size=67108864
max_used_connections=10
max_threads=48
thread_count=56
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6308889 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x2271884e578
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...
2024-01-28 19:20:08 197681 [Note] something private
2024-01-28 19:20:08 197681 [Note] something private
2024-01-28 19:20:08 197681 [Note] something private
2024-01-28 19:20:08 197681 [Note] something private
2024-01-28 19:20:08 197681 [Note] something private
server.dll!row_fts_psort_info_destroy()[row0ftsort.cc:336]
server.dll!row_fts_psort_info_init()[row0ftsort.cc:303]
server.dll!row_merge_build_indexes()[row0merge.cc:4766]
server.dll!ha_innobase::inplace_alter_table()[handler0alter.cc:8814]
server.dll!mysql_inplace_alter_table()[sql_table.cc:7796]
server.dll!mysql_alter_table()[sql_table.cc:10989]
server.dll!mysql_recreate_table()[sql_table.cc:12096]
server.dll!admin_recreate_table()[sql_admin.cc:71]
server.dll!mysql_admin_table()[sql_admin.cc:1232]
server.dll!Sql_cmd_optimize_table::execute()[sql_admin.cc:1620]
server.dll!mysql_execute_command()[sql_parse.cc:6039]
server.dll!Prepared_statement::execute()[sql_prepare.cc:5267]
server.dll!Prepared_statement::execute_loop()[sql_prepare.cc:4668]
server.dll!mysql_sql_stmt_execute()[sql_prepare.cc:3701]
server.dll!mysql_execute_command()[sql_parse.cc:3978]
server.dll!sp_instr_stmt::exec_core()[sp_head.cc:3923]
server.dll!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:3646]
server.dll!sp_instr_stmt::execute()[sp_head.cc:3827]
server.dll!sp_head::execute()[sp_head.cc:1463]
server.dll!sp_head::execute_procedure()[sp_head.cc:2479]
server.dll!Event_job_data::execute()[event_data_objects.cc:1482]
server.dll!event_worker_thread()[event_scheduler.cc:268]
server.dll!pfs_spawn_thread()[pfs.cc:2204]
server.dll!pthread_start()[my_winthread.c:62]
ucrtbase.dll!_recalloc()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2270e6a4960): OPTIMIZE NO_WRITE_TO_BINLOG TABLE `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`
Connection ID (thread ID): 197689
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,hash_join_cardinality=off,cset_narrowing=off
 
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\Program Files\MariaDB\data
Minidump written to C:\Program Files\MariaDB\data\mysqld.dmp



 Comments   
Comment by Alice Sherepa [ 2024-01-29 ]

Is it possible for you to add the output of SHOW CREATE TABLE for that table? You could upload it to the private section of MariaDB FTP server (https://mariadb.com/kb/en/meta/mariadb-ftp-server/ ), so nobody but MariaDB developers would have access to it

Comment by Mitchell Lee [ 2024-01-29 ]

@Alice Sherepa Erm... to know the reason why you ask, it should be....
the log itself telling about crash when object creation?

Comment by Alice Sherepa [ 2024-01-30 ]

We need a way to repeat the crash on our side. Ideally, you would provide a test case to demonstrate the problem or at least the details and scenario. Of course please obfuscate everything private, etc. Was it only a one-time crash or is it repeatable? Was it event/stored procedure/trigger and inside that there is a prepared statement? What non-default configuration do you use (.cnf file(s))?

Comment by Mitchell Lee [ 2024-01-30 ]

Seems non-repeatable since tons of similar queries excuted/executing before, and now.
So...have no idea which query actually involved to the issue,
BUT,
if you suspect any 'object creation', it would be below was in the prepared statement.
------------------
CREATE EVENT `XXXXXXXXXXXX`
ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 second
ON COMPLETION NOT PRESERVE
ENABLE
DO
something something
------------------

And of cuz, not a default config.

Generated at Thu Feb 08 10:38:02 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.