-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
C++: Valgrind Memory leak #14794
Comments
Fixes #14794 PiperOrigin-RevId: 583499526
Fixes #14794 PiperOrigin-RevId: 583499526
Fixes #14794 PiperOrigin-RevId: 583499526
Fixes protocolbuffers#14794 PiperOrigin-RevId: 583499526
FWIW this is a fixed-size global that doesn't represent any kind of dangerous leak, but I'll added a deleter to clean it up |
@mkruskal-google
Is this related in any way? Do I have to do some clean up? Context: Since this is some static initialization/allocation done before the program really starts I guess it is save to suppress it, right? But I would be more relaxed if I could get rid of these Valgrind issues :) |
What version of protobuf and what language are you using?
Version: 4.25.0 (archlinux protobuf version 25.0-1) (absl version 20230802.1-1)
Language: C++
What operating system (Linux, Windows, ...) and version?
Linux (arch 6.6.1-arch1-1)
What runtime / compiler are you using (e.g., python version or gcc version)
gcc 13.2.1 20230801
clang 16.0.6
What did you do?
Steps to reproduce the behavior:
Example proto:
Example code:
What did you expect to see
No leak as with versions <=4.24
What did you see instead?
Error
Anything else we should know about your project / environment
ASAN does not indicate anything, so this might be an valgrind thing. Also happens if google::protobuf::util::MessageToJsonString is called.
The text was updated successfully, but these errors were encountered: