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

[BUG] Memory Leak if ADB Android is locked #862

Open
gamestailer94 opened this issue Dec 27, 2022 · 0 comments
Open

[BUG] Memory Leak if ADB Android is locked #862

gamestailer94 opened this issue Dec 27, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@gamestailer94
Copy link

gamestailer94 commented Dec 27, 2022

Describe the bug
I use an old Android as the Screen, as described here via USB(ADB).
When I lock the Android Phone, (because I go to bed) Klipper Screen starts using more and more memory, at about 1 MB / min.
It stops if I unlock the phone and some memory gets freed, but not all. (110MB before unlock, after unlock 91MB, normal is 68MB)
I did only test it while a print was running.

I created a memory usage log, using this script

Android used, if relevant:
Samsung Galaxy Note Edge (SM-N915FY)
Android 8.1.0

To Reproduce
Connect Android as a Screen via USB ADB
Start monitoring the memory of klipper screen python script
Lock the Phone
Memory usage of script starts to increase

Expected behavior
To not use more memory

Logfile
memory_usage.log
KlipperScreen.log

@alfrix alfrix added the bug Something isn't working label Oct 15, 2023
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

2 participants