Mariadb process crashed after running store procedure

The database is migrated from MySQL 5.7.24 to Marialdb 10.4.7 via mysqldump. The store procedures are running without problem on MySQL. However, the mysqld process is crashed after migrated to Marialdb either running with 1 node or 2 node cluster.

191003 12:12:00 [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.7-MariaDB-log
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=33
max_threads=602
thread_count=43
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1509816 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc060007b28
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 = 0x7fc158262d30 thread_stack 0x49000
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5619a86ce6be]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x5619a815d81f]
sigaction.c:0(__restore_rt)[0x7fc1807645e0]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN4JOIN7destroyEv+0x20)[0x5619a7f930b0]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN13st_select_lex7cleanupEv+0x68)[0x5619a7ff4648]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN30subselect_single_select_engine7prepareEP3THD+0x44)[0x5619a8213ae4]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0x135)[0x5619a82134d5]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN9Item_cond10fix_fieldsEP3THDPP4Item+0x2c0)[0x5619a8199fe0]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN3THD16sp_fix_func_itemEPP4Item+0x90)[0x5619a7eb5c40]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN3THD20sp_prepare_func_itemEPP4Itemj+0xf)[0x5619a7eb5c5f]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN20sp_instr_jump_if_not9exec_coreEP3THDPj+0x1e)[0x5619a7eb5cae]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x155)[0x5619a7ebbb65]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x9dc)[0x5619a7eb77dc]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x779)[0x5619a7eb8ab9]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(+0x68897a)[0x5619a7f4597a]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(+0x68a2b6)[0x5619a7f472b6]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN12Sql_cmd_call7executeEP3THD+0x90)[0x5619a7f47af0]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x31e8)[0x5619a7f508e8]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x4b6)[0x5619a7f6b0f6]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(ZN18Prepared_statement12execute_loopEP6StringbPhS2+0x92)[0x5619a7f6b2b2]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(+0x6aec17)[0x5619a7f6bc17]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x27)[0x5619a7f6bca7]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x17e2)[0x5619a7f59c02]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_Z10do_commandP3THD+0x11c)[0x5619a7f5befc]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x241)[0x5619a80390a1]
/u01/app/mariadb/10.4.7/usr/sbin/mysqld(handle_one_connection+0x3d)[0x5619a80391fd]
pthread_create.c:0(start_thread)[0x7fc18075ce25]
/lib64/libc.so.6(clone+0x6d)[0x7fc17ed3434d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fc060fd1180): is an invalid pointer
Connection ID (thread ID): 3364
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=off,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: call stp_dashboard_info_update(?, ?, ?)

Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 0 bytes
Max resident set unlimited unlimited bytes
Max processes 31139 31139 processes
Max open files 3005 3005 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31139 31139 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core