Closed billyors closed 2 weeks ago
Are you monitoring the PlexCleaner process memory usage, or docker memory usage, or your host system memory usage?
Did you capture any data for the process memory usage over time, or can correlate it with file count?
Was there anything in particular in IsMediaCurrent()
or ComputeHash()
that you suspect is leaking, consider that the only memory allocations are being made in ComputeHash()
, and that happens for all modified and new files, and the garbage collector does cleanup, this is C# not C++?
If you were monitoring host system or docker subsystem memory usage, refer to the readme on tuning your docker log that can consume large amounts of memory.
Closing due to no response.
Is this a new issue that can be reproduced using the latest version?
Which operating systems reproduce the issue?
Version information.
OS Version: Ubuntu 24.04 Docker Version: 26.1.1, build 4cf5afa Docker Image:
latest
PlexCleaner getversioninfo
: 3.8.19.46621 (Release)Steps to reproduce?
I'm a little out of my element looking at this code but I think there is a potential memory leak during processing. I think the issue is related to the
IsMediaCurrent
code.Steps to reproduce the behavior:
Sidecar LastWriteTimeUtc out of sync with media file
andSidecar SHA256 out of sync with media file
.Expected: Memory usage should remain stable and not increase excessively during processing.
Commandline.
Relevant log output.
Settings file.
settings.json
Log file.
No response
Media file information.