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

After closing KCF tracker , the memory didn't release completely. #7

Open
r1c7 opened this issue Aug 15, 2018 · 4 comments
Open

After closing KCF tracker , the memory didn't release completely. #7

r1c7 opened this issue Aug 15, 2018 · 4 comments

Comments

@r1c7
Copy link

r1c7 commented Aug 15, 2018

I found even if i closed KCF tracking, RAM usage dropped,but didn't release completely(according to the tracker_box, maybe 2% or higher).
Such as, I run the tracker in a child thread, and the main thread just loops(do nothing) after the child thread closed.
What causes this problem?

@rockkingjy
Copy link
Owner

@crsailing thanks for your feed-back, I will check later.

@rockkingjy
Copy link
Owner

hi, one question, what kind of tools you've used for monitor RAM? I didn't see any abnormal leakage here.

@r1c7
Copy link
Author

r1c7 commented Nov 8, 2018

@rockkingjy I used htop in Linux.

@isgursoy
Copy link

https://github.com/KDE/heaptrack is better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants