Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible mem issue in keyvault keys #4434

Open
gearama opened this issue Mar 10, 2023 · 0 comments
Open

Possible mem issue in keyvault keys #4434

gearama opened this issue Mar 10, 2023 · 0 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. KeyVault

Comments

@gearama
Copy link
Member

gearama commented Mar 10, 2023

valgrind --leak-check=full --track-origins=yes --show-leak-kinds=all ./azure-security-keyvault-keys-test &> key_mem.txt

==12193==
==12193== HEAP SUMMARY:
==12193== in use at exit: 4,760 bytes in 10 blocks
==12193== total heap usage: 3,436,666 allocs, 3,436,656 frees, 259,573,377 bytes allocated
==12193==
==12193== 4,760 bytes in 10 blocks are definitely lost in loss record 1 of 1
==12193== at 0x484A2F3: operator new[](unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==12193== by 0x256E9C: Azure::Security::KeyVault::Keys::Test::MockedTransportAdapter::UpdateFakeKey(char const*, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) (mocked_transport_adapter_test.hpp:94)
==12193== by 0x256A17: Azure::Security::KeyVault::Keys::Test::MockedTransportAdapter::Send(Azure::Core::Http::Request&, Azure::Core::Context const&) (mocked_transport_adapter_test.hpp:55)
==12193== by 0x31B9B0: Azure::Core::Http::Policies::_internal::TransportPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Http::Policies::NextHttpPolicy, Azure::Core::Context const&) const (transport_policy.cpp:120)
==12193== by 0x314FD1: Azure::Core::Http::Policies::NextHttpPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Context const&) (policy.cpp:21)
==12193== by 0x312C44: Azure::Core::Http::Policies::_internal::LogPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Http::Policies::NextHttpPolicy, Azure::Core::Context const&) const (log_policy.cpp:114)
==12193== by 0x314FD1: Azure::Core::Http::Policies::NextHttpPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Context const&) (policy.cpp:21)
==12193== by 0x317123: Azure::Core::Http::Policies::_internal::RequestActivityPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Http::Policies::NextHttpPolicy, Azure::Core::Context const&) const (request_activity_policy.cpp:110)
==12193== by 0x314FD1: Azure::Core::Http::Policies::NextHttpPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Context const&) (policy.cpp:21)
==12193== by 0x318B9E: Azure::Core::Http::Policies::_internal::RetryPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Http::Policies::NextHttpPolicy, Azure::Core::Context const&) const (retry_policy.cpp:141)
==12193== by 0x314FD1: Azure::Core::Http::Policies::NextHttpPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Context const&) (policy.cpp:21)
==12193== by 0x31B461: Azure::Core::Http::Policies::_internal::TelemetryPolicy::Send(Azure::Core::Http::Request&, Azure::Core::Http::Policies::NextHttpPolicy, Azure::Core::Context const&) const (telemetry_policy.cpp:23)
==12193==
==12193== LEAK SUMMARY:
==12193== definitely lost: 4,760 bytes in 10 blocks
==12193== indirectly lost: 0 bytes in 0 blocks
==12193== possibly lost: 0 bytes in 0 blocks
==12193== still reachable: 0 bytes in 0 blocks
==12193== suppressed: 0 bytes in 0 blocks
==12193==
==12193== For lists of detected and suppressed errors, rerun with: -s
==12193== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 10, 2023
@gearama gearama added bug This issue requires a change to an existing behavior in the product in order to be resolved. KeyVault and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Mar 10, 2023
@RickWinter RickWinter added the Client This issue points to a problem in the data-plane of the library. label Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
None yet
Development

No branches or pull requests

2 participants