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

Free allocated X resource value. #2620

Merged
merged 1 commit into from Jan 2, 2017
Merged

Conversation

Airblader
Copy link
Member

This fixes a little memory leak.

This fixes a little memory leak.
@Airblader
Copy link
Member Author

There seems to be a really bad memory leak in i3bar. I'm leaking dozens of MB in a few minutes and it doesn't seem to end. I'm not convinced it's an i3bar issue, but I'm still looking into it. If somebody could monitor i3bar on their end to see if it's just me that'd be pretty cool.

@Airblader
Copy link
Member Author

Airblader commented Dec 31, 2016

Not using a pango font I get a constant and low memory usage, opposed to the 0.5 GB I already accumulated in the past twenty minutes or so when using a pango font.

However, it's interesting that only i3bar has the issue, not i3 itself despite font handling being in libi3.

@Airblader
Copy link
Member Author

The leak seems to have come to a halt at 444 MB now. Which is still way beyond what i3bar should need. I'm fairly convinced this is a bug in pango or fontconfig, though.

@stapelberg stapelberg merged commit 25d27c5 into i3:next Jan 2, 2017
syrrim pushed a commit to syrrim/i3 that referenced this pull request Feb 3, 2017
This fixes a little memory leak.
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

Successfully merging this pull request may close these issues.

None yet

2 participants