Fix SDL cursors memory leak #1012
Merged
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.
Fixes #587. When using the SDL backend, cursors were created every frame but not being freed by
SDL_FreeCursor
(in fact they were not even tracked at all). This led the Xorg server cursor memory to fill up and never be freed, ending up requiring restarting X.This issue did not happen when using the Sokol backend.
xrestop
makes it easy to figure this leak out, whiletic80
is running