Skip to content

Fix valgrind reachable memleak error#4919

Open
francando wants to merge 1 commit intogoogle:mainfrom
francando:fix/valgrind_reachable_memleak
Open

Fix valgrind reachable memleak error#4919
francando wants to merge 1 commit intogoogle:mainfrom
francando:fix/valgrind_reachable_memleak

Conversation

@francando
Copy link

Fix for #4109

@google-cla
Copy link

google-cla bot commented Jan 30, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@francando francando force-pushed the fix/valgrind_reachable_memleak branch from 7dab4ee to aa135c8 Compare January 30, 2026 17:28
@francando francando force-pushed the fix/valgrind_reachable_memleak branch from aa135c8 to b3c449c Compare February 3, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant