[Bug]: unit test may have mem leak caused by gtest framework

[zhengbuqian]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: master

Current Behavior

in master branch, always enable asan by modify

from:

    if ( USE_ASAN AND false )
        message( STATUS "Building Milvus using AddressSanitizer")
        add_compile_options(-fno-stack-protector -fno-omit-frame-pointer -fno-var-tracking -fsanitize=address)
        add_link_options(-fno-stack-protector -fno-omit-frame-pointer -fno-var-tracking -fsanitize=address)
    endif()

to:

#    if ( USE_ASAN AND false )
        message( STATUS "Building Milvus using AddressSanitizer")
        add_compile_options(-fno-stack-protector -fno-omit-frame-pointer -fno-var-tracking -fsanitize=address)
        add_link_options(-fno-stack-protector -fno-omit-frame-pointer -fno-var-tracking -fsanitize=address)
#    endif()

then make test-cpp to build unit test with asan enabled.

Run ./internal/core/output/unittest/all_tests --gtest_list_tests. NO test will be ran, but after gtest listed all test cases, asan reported memory leak.

it seems the mem leak is caused by gtest, not our code?

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[zhengbuqian]

or could it be a globally allocated memory?

[PwzXxm]

Maybe caused by some static test suite initialization