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

Valgrind mem leaks findings #114

Closed
M-F-K opened this issue Dec 17, 2012 · 3 comments
Closed

Valgrind mem leaks findings #114

M-F-K opened this issue Dec 17, 2012 · 3 comments
Assignees
Milestone

Comments

@M-F-K
Copy link
Collaborator

M-F-K commented Dec 17, 2012

This issue is created to hold valgrind findings from the tutorials / tests etc. Each entry should be a reference from a commit with comments where the code leaks.

@DarthMike
Copy link
Owner

Moved to M0.6

M-F-K added a commit that referenced this issue Jun 15, 2013
@M-F-K
Copy link
Collaborator Author

M-F-K commented Jun 15, 2013

As far as I can see it, we only have the uninitilized key event left..

@M-F-K
Copy link
Collaborator Author

M-F-K commented Sep 29, 2013

Since we only have the unitialize key event left ( and it is marked with a TODO ) and we have to do some alteration in regards to issue #67 . I think we can safely close this issue.

@M-F-K M-F-K closed this as completed Sep 29, 2013
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