为了更快的定位您的问题，请提供以下信息，谢谢
【详述】运行udf方法导致be异常重启
【背景】创建了一个udf方法执行后be就会异常重启 三台be节点都会重启 udf方法在别的几个sr版本都是运行正常的，换了一个3.2.11的环境运行正常 只有这个环境有问题 需要怎么排查问题并恢复？
【业务影响】
【是否存算分离】
【StarRocks版本】3.2.11
【集群规模】例如：3fe（1 follower+2observer）+5be（fe与be混部）
【机器信息】CPU虚拟核/内存/网卡，例如：48C/64G/万兆
【联系方式】社区群22 hpp
【附件】
I0206 14:37:26.207415 716 internal_service.cpp:442] exec plan fragment, fragment_instance_id=d44a00dd-e454-11ef-a122-02427c5c45b2, coord=TNetworkAddress(hostname=node-01, port=9020), backend=6, is_pipeline=1, chunk_size=4096
I0206 14:37:26.207433 716 fragment_executor.cpp:183] Prepare(): query_id=d44a00dd-e454-11ef-a122-02427c5c45ab fragment_instance_id=d44a00dd-e454-11ef-a122-02427c5c45b2 is_stream_pipeline=0 backend_num=6
I0206 14:37:26.255064 716 logconfig.cpp:133] je_mallctl execute dontdump success
[Thu Feb 6 14:37:34 CST 2025] Last 50 lines of be.out …
tracker:short_key_index consumption: 0
tracker:column_zonemap_index consumption: 17920
tracker:ordinal_index consumption: 15280
tracker:bitmap_index consumption: 0
tracker:bloom_filter_index consumption: 0
tracker:compaction consumption: 0
tracker:schema_change consumption: 0
tracker:column_pool consumption: 0
tracker:page_cache consumption: 2464
tracker:update consumption: 404902760
tracker:chunk_allocator consumption: 1606848
tracker:clone consumption: 0
tracker:consistency consumption: 0
tracker:datacache consumption: 0
tracker:replication consumption: 0
*** Aborted at 1738823846 (unix time) try “date -d @1738823846” if you are using GNU date ***
PC: @ 0x7f97128d3d04 AccessInternal::PostRuntimeDispatch<>::oop_access_barrier()
*** SIGSEGV (@0x0) received by PID 25 (TID 0x7f9661554640) from PID 0; stack trace: ***
@ 0x849d15a google::(anonymous namespace)::FailureSignalHandler()
@ 0x7f9712f51916 os::Linux::chained_handler()
@ 0x7f9712f5760b JVM_handle_linux_signal
@ 0x7f9712f4a46c signalHandler()
@ 0x7f9712073520 (unknown)
@ 0x7f97128d3d04 AccessInternal::PostRuntimeDispatch<>::oop_access_barrier()
@ 0x7f9712c544f1 get_method_id()
@ 0x7f9712c54816 jni_GetStaticMethodID
@ 0x7d2b0f7 methodIdFromClass
@ 0x7d2b1ca invokeMethodOnJclass
@ 0x7d2b6c9 invokeMethod
@ 0x7d2c6bb getExceptionUtilString
@ 0x7d2c8ed printExceptionAndFreeV
@ 0x7d2cade printExceptionAndFree
@ 0x7d2c0d6 getJNIEnv
@ 0x6f0ab58 starrocks::JVMFunctionHelper::getInstance()
@ 0x6f10252 starrocks::ClassLoader::init()
@ 0x42b97f1 starrocks::JavaFunctionCallExpr::_build_udf_func_desc()
@ 0x42baa66 _ZNSt17_Function_handlerIFN9starrocks6StatusEvEZZNS0_20JavaFunctionCallExpr4openEPNS0_12RuntimeStateEPNS0_11ExprContextENS0_15FunctionContext18FunctionStateScopeEENKUlRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEE_clESH_EUlvE_E9_M_invokeERKSt9_Any_data
@ 0x6f05160 starrocks::call_function_in_pthread()
@ 0x42baf3a ZZN9starrocks20JavaFunctionCallExpr4openEPNS_12RuntimeStateEPNS_11ExprContextENS_15FunctionContext18FunctionStateScopeEENKUlRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEE_clESE
@ 0x42bcd1e starrocks::JavaFunctionCallExpr::open()
@ 0x42a45b8 starrocks::Expr::open()
@ 0x42cdd8d starrocks::VectorizedFunctionCallExpr::open()
@ 0x42a45b8 starrocks::Expr::open()
@ 0x42a45b8 starrocks::Expr::open()
@ 0x42bca99 starrocks::JavaFunctionCallExpr::open()
@ 0x42a45b8 starrocks::Expr::open()
@ 0x42cdd8d starrocks::VectorizedFunctionCallExpr::open()
@ 0x42a45b8 starrocks::Expr::open()
@ 0x42ab16e starrocks::ExprContext::open()
@ 0x42a47b0 starrocks::Expr::open()
[Thu Feb 6 14:37:35 CST 2025] Empty $CONFIGMAP_MOUNT_PATH env var, skip it!
[Thu Feb 6 14:37:35 CST 2025] Add myself (node-02:9050) into FE …
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1064 (HY000) at line 1: Unexpected exception: Backend already exists with same host node-02 and port 9050
mysql: [Warning] Using a password on the command line interface can be insecure.
select udf_xxx(‘zxcv’,‘x’,‘c’);
ERROR 1064 (HY000): rpc failed with node-00: exec rpc error. backend [id=10006] [host=node-00]
随便跑一个udf相关的函数就会导致be出现报错重启