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

There is at least one more memory leak in xpyb #395

Closed
tych0 opened this issue Apr 1, 2014 · 2 comments
Closed

There is at least one more memory leak in xpyb #395

tych0 opened this issue Apr 1, 2014 · 2 comments

Comments

@tych0
Copy link
Member

tych0 commented Apr 1, 2014

This isn't really a qtile bug, but I think it is up to us to fix it since upstream isn't really that active.

2014-04-01 14:33:21 dx  the "test case" http://ix.io/9P1/diff
2014-04-01 14:33:48 dx  my fix attempt which miraculously doesn't segfault but makes events disappear https://github.com/dequis/xpyb/commit/event_memleak
2014-04-01 14:35:54 dx  valgrind output snippets http://ix.io/9P7 http://ix.io/9P8
@zordsdavini
Copy link
Contributor

Do we use this lib anymore?

@tych0
Copy link
Member Author

tych0 commented Feb 11, 2015

Ah ha, no, we don't :)

@tych0 tych0 closed this as completed Feb 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants