You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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
The text was updated successfully, but these errors were encountered: