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

Memory Leak #395

Closed
QiAnXinCodeSafe opened this issue Dec 18, 2019 · 2 comments
Closed

Memory Leak #395

QiAnXinCodeSafe opened this issue Dec 18, 2019 · 2 comments

Comments

@QiAnXinCodeSafe
Copy link

Memory is allocated


Potential leak of memory pointed to by 'newBuf '

@jonathanvmw
Copy link
Contributor

Thanks for reporting this issue. Can you provide any additional background? For example, was this issue reported by a code analysis tool and if so which one? Was there any additional analysis provided?

At the moment this looks like a false positive. If the code reaches line 552, it implies the call to DataMap_SetString at line 539 was successful; this would attach to map the storage pointed to by newBuf. The call to DataMap_Destroy at line 551 would then free that storage as part of freeing map.

@QiAnXinCodeSafe
Copy link
Author

Hi,Thank you for your quickly feedback, This issue found by our own symbolic-execution-based static analyzer.

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

No branches or pull requests

2 participants