Merged
Conversation
milianw
reviewed
Dec 11, 2024
lievenhey
force-pushed
the
fix-memory-leaks
branch
from
091da7e to
2db8a17
Compare
Contributor
Author
|
Seems like the leaks you where wondering about (me too) were caused by a qt/plasma bug. After updating they no longer appear. (Still get wayland leaks but I can deal with them, before it were hundreds) |
milianw
force-pushed
the
fix-memory-leaks
branch
from
2db8a17 to
a74e889
Compare
Contributor
|
Should this 4-line change be pulled in or is it not relevant any more (further leaks, if there are some, could always be coped with a follow-up PR)? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.