[DocDB] ASAN leak in RemoteBootstrapAnchorClient::KeepLogAnchorAliveAsync #16061
Labels
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
kind/failing-test
Tests and testing infra
priority/high
High Priority
Jira Link: DB-5454
Description
https://detective-gcp.dev.yugabyte.com/job/yugabyte-db-phabricator%2F88142%2Fartifact%2Fbuild%2Fasan-clang15-dynamic-ninja%2Fyb-test-logs%2Ftests-integration-tests__remote_bootstrap-itest%2FRemoteBootstrapITest_TestRemoteBootstrapFromClosestPeer.log?class=RemoteBootstrapITest&name=TestRemoteBootstrapFromClosestPeer
https://detective-gcp.dev.yugabyte.com/job/yugabyte-db-phabricator%2F88142%2Fartifact%2Fbuild%2Fasan-clang15-dynamic-ninja%2Fyb-test-logs%2Ftests-integration-tests__remote_bootstrap-itest%2FRemoteBootstrapITest_TestBootstrapSourceCrashesWhileFetchingData.log?class=RemoteBootstrapITest&max_lines=3000&name=TestBootstrapSourceCrashesWhileFetchingData&start_line=3001
Seems like a pretty obvious leak, where we new a response, but there's no smart pointers around it's ownership to delete the memory. cc @amitanandaiyer @rthallamko3
This seems like a product leak too! Release wise, this is in 2.16.
The text was updated successfully, but these errors were encountered: