[Bug] Doris BE crashed with SIGSEGV when executing a query; version 3.0.6.2

[frankqoqo8]

Search before asking

• I had searched in the issues and found no similar issues.

Version

Current BE git commitID: 910c424

What's Wrong?

Doris backend crashed with SIGSEGV (segmentation fault) during query execution.

Relevant log:
*** Query id: 65948afbc49b4bed-a09c3d6732a699d8 ***
*** is nereids: 0 ***
*** tablet id: 0 ***
*** Aborted at 1753705295 (unix time) try "date -d @1753705295" if you are using GNU date ***
*** Current BE git commitID: 910c424 ***
*** SIGSEGV unknown detail explain (@0x0) received by PID 107308 (TID 31159 OR 0x7f618b965700) from PID 0; stack trace: ***
0# doris::signal::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*) at /home/zcp/repo_center/doris_release/doris/be/src/common/signal_handler.h:421
1# PosixSignals::chained_handler(int, siginfo*, void*) [clone .part.0] in /opt/tools/jdk-17.0.12//lib/server/libjvm.so
2# JVM_handle_linux_signal in /opt/tools/jdk-17.0.12//lib/server/libjvm.so
3# 0x00007F6FC3E6A400 in /lib64/libc.so.6
4# doris::TUniqueId::TUniqueId(doris::TUniqueId const&) at /home/zcp/repo_center/doris_release/doris/gensrc/build/gen_cpp/Types_types.cpp:2509
5# doris::AttachTask::AttachTask(doris::QueryContext*) at /home/zcp/repo_center/doris_release/doris/be/src/runtime/thread_context.cpp:61
6# std::_Function_handler<void (), doris::pipeline::PipelineFragmentContext::_build_pipeline_tasks(doris::TPipelineFragmentParams const&, doris::ThreadPool*)::$_1>::_M_invoke(std::_Any_data const&) at /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/std_function.h:291
7# doris::ThreadPool::dispatch_thread() in /data/doris/apache-doris-3.0.6.2-bin-x64/be/lib/doris_be
8# doris::Thread::supervise_thread(void*) at /home/zcp/repo_center/doris_release/doris/be/src/util/thread.cpp:499
9# start_thread in /lib64/libpthread.so.0
10# clone in /lib64/libc.so.6

What You Expected?

Doris BE should not crash. The query should complete or return an error gracefully instead of causing a segmentation fault.

How to Reproduce?

Unfortunately, the exact SQL and cluster setup are not available, but the attached stack trace and commit id should help locate the issue.

Anything Else?

Please check if recent changes in thread context or TUniqueId may relate to this issue.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct