fix sharedptr , weakptr implentation leak #1
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.
if we dont decrement the sharedptr on destruction any weakptr remaining will have an impl_ with a ref of 1 and upon destruction of the weakptr it wont delete the implentation because it thinks a shared pointer still exist.
as in
hyprutils/include/hyprutils/memory/SharedPtr.hpp
Line 175 in 0693f93
hyprutils/include/hyprutils/memory/WeakPtr.hpp
Line 171 in 0693f93
destroyImpl() also already checks for weakptr ref before deleting impl so the comment section in the old destruction logic shouldnt be true.
leak can be seen in the hyprutils_memory test or hyprland itself