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

Diagnose memory profiling to ensure there are no memory leaks on objects created [CPU] #15

Closed
axsaucedo opened this issue Aug 30, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@axsaucedo
Copy link
Member

Use memory profiler to perform initial assessment for any potential obvious non exhaustive memory leaks that may be left due to references to pointer objects that are not freed, as well as potentially Vulkan resources that are not freed

@axsaucedo
Copy link
Member Author

Running diagnostics it seems there are some objects that are not being freed resulting in reference counts.
Memory profile overview:
image

Current non-destroyed kp components:
image

Current non-destroyed vulkan components:
image

@axsaucedo axsaucedo added the bug Something isn't working label Aug 30, 2020
@axsaucedo
Copy link
Member Author

This has been fixed via 5be21da

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant