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.

Sign up for GitHub

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

Jump to bottom

Identify and Fix Remaining Memory Leaks #11

Closed
emcd opened this issue Feb 9, 2013 · 2 comments
Closed

Identify and Fix Remaining Memory Leaks #11

emcd opened this issue Feb 9, 2013 · 2 comments
Labels
bug theme:best-practices theme:customer-oriented
Milestone
1.0 release

Comments

@emcd
Copy link
Contributor

emcd commented Feb 9, 2013

Any remaining memory leaks should be identified and fixed before an official release.
@ghost ghost assigned emcd Feb 9, 2013
@emcd emcd mentioned this issue Mar 26, 2013
Closed
@mr-c
Copy link
Contributor

mr-c commented Jul 28, 2013

Update: several memory leaks have been found via coverity static analysis. Fixes are forthcoming

@mr-c
Copy link
Contributor

mr-c commented Aug 20, 2013

Coverity memory leak fixes are in.

@mr-c mr-c closed this as completed Aug 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug theme:best-practices theme:customer-oriented
Projects
None yet
Milestone
1.0 release
Development

No branches or pull requests
2 participants
@emcd @mr-c