Ensure GFile is unreferenced to avoid filename memory leak #3
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.
Hello @federicomenaquintero, thank you very much for all the time you continue to devote to librsvg.
v2.40.20 appears to have introduced a small memory leak of the filename that I think was via the change in commit 475764f
The change in this PR should ensure the GFile instance is unreferenced for all paths.
(The Gnome GitLab instance won't let me register - "Email is not from an allowed domain" - hence the use of GitHub.)