-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix trivial leak in ThreadFilter #131
Conversation
🔧 Report generated by pr-comment-scanbuild Scan-Build Report
Bug Summary
Reports
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no functional impact but keeps tsan happy?
This was actually not pointed out by tsan - and we are not running it by default anyway. |
What does this PR do?:
It fixes a trivial leak when the destructor of
ThreadFilter
class did not release the memory allocated for_bitmaps
.Motivation:
Mostly just a code cleanup - with our current usage the
ThreadFilter
instance will remain active during the whole lifespan of the profiled application so the memory would not really 'leak'. But it is better to have a correct destructor if the usage ofThreadFilter
would change in the future.Additional Notes:
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!