Server crash when using "SET STATEMENT max_statement_time=N FOR desc xxx" lead to collapse

mariadb version (known):
10.4.10
10.4.11
10.4.12

execute:
SET STATEMENT max_statement_time=0 FOR desc table
max_statement_time any value，any table，the server must be crash.

Log:

200131 20:56:30 [ERROR] mysqld got signal 11 ;
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.4.11-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=2
max_threads=153
thread_count=8
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467745 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fec32089808
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...
stack_bottom = 0x700010535eb0 thread_stack 0x49000
0 mysqld 0x000000010207ee24 my_print_stacktrace + 60
0 mysqld 0x0000000101a46fc4 handle_fatal_signal + 720
0 libsystem_platform.dylib 0x00007fff7c798b3d _sigtramp + 29
0 ??? 0x00007fec3208f3d0 0x0 + 140652428456912
0 mysqld 0x0000000101bfa676 _Z17mysql_init_selectP3LEX + 21
0 mysqld 0x0000000101d86a05 _Z10MYSQLparseP3THD + 35771
0 mysqld 0x0000000101bfaba0 _Z9parse_sqlP3THDP12Parser_stateP19Object_creation_ctxb + 131
0 mysqld 0x0000000101bed46c _Z11mysql_parseP3THDPcjP12Parser_statebb + 306
0 mysqld 0x0000000101beaebe _Z16dispatch_command19enum_server_commandP3THDPcjbb + 1463
0 mysqld 0x0000000101bed925 _Z10do_commandP3THD + 587
0 mysqld 0x0000000101ccefb6 _Z24do_handle_one_connectionP7CONNECT + 346
0 mysqld 0x0000000101ccee4f handle_one_connection + 56
0 libsystem_pthread.dylib 0x00007fff7c7a1339 _pthread_body + 126
0 libsystem_pthread.dylib 0x00007fff7c7a42a7 _pthread_start + 70
0 libsystem_pthread.dylib 0x00007fff7c7a0445 thread_start + 13

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fec318fc820): is an invalid pointer
Connection ID (thread ID): 16
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

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.

We think the query pointer is invalid, but we will try to print it anyway.
Query: SET STATEMENT max_statement_time=0 FOR desc mysql.user