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

Removed the cause of a huge memory leak #149

Merged
merged 1 commit into from
Aug 27, 2019
Merged

Removed the cause of a huge memory leak #149

merged 1 commit into from
Aug 27, 2019

Conversation

tsujan
Copy link
Member

@tsujan tsujan commented Aug 27, 2019

This patch removes a huge memory leak in Proc::refresh().

NOTE: It may seem that there is still a relatively smaller memory leak in setting the graph as the tray and window icon. However, the increase in memory usage stops after a while. So, this closes #101

This patch removes a huge memory leak in `Proc::refresh()`.

NOTE: It may seem that there is still a relatively smaller memory leak in setting the graph as the tray and window icon. However, the increase in memory usage stops after a while. So, this closes #101
@tsujan tsujan mentioned this pull request Aug 27, 2019
@shlyakpavel
Copy link
Member

Looks good. Why do not you merge it now?

@tsujan
Copy link
Member Author

tsujan commented Aug 27, 2019

Why do not you merge it now?

Each PR needs the approval of another dev -- in this case, you gave it by saying "looks good".

It definitely removes a big memory leak. If there's still a leak, it should be small but Qt's setIcon sometimes shows a "leak-like" behavior while there's no real leak.

Please continue finding and fixing issues in qps's code! Functions with return at their starts, redundant codes, redundant comments, etc., make it hard to read the code. Later, we could modernize the GUI part.

@tsujan tsujan merged commit 44619b5 into master Aug 27, 2019
@tsujan tsujan deleted the fix_huge_leak branch August 27, 2019 11:38
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.

Potential memory leaks
2 participants