We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We found one memory leak bug while running atomic-server. Here is the bug report from the sanitizer:
Direct leak of 56 byte(s) in 1 object(s) allocated from: -- #0 0x71f63d in operator new(unsigned long) (/opt/fs/braft/example/atomic/atomic_server+0x71f63d) #1 0xd4f40f in brpc::Server::StartInternal(butil::EndPoint const&, brpc::PortRange const&, brpc::ServerOptions const*) /opt/fs/brpc/src/brpc/server.cpp:834:22 #2 0xd5249f in brpc::Server::Start(butil::EndPoint const&, brpc::ServerOptions const*) /opt/fs/brpc/src/brpc/server.cpp:1131:12 #3 0xd5249f in brpc::Server::Start(int, brpc::ServerOptions const*) /opt/fs/brpc/src/brpc/server.cpp:1150:12 #4 0x72331e in main /opt/fs/braft/example/atomic/server.cpp:501:16 #5 0x7ffff719b09a in __libc_start_main /build/glibc-6iIyft/glibc-2.28/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: 56 byte(s) leaked in 1 allocation(s).
The text was updated successfully, but these errors were encountered:
related issue: apache/brpc#2164
Sorry, something went wrong.
No branches or pull requests
We found one memory leak bug while running atomic-server. Here is the bug report from the sanitizer:
The text was updated successfully, but these errors were encountered: