Memory leak about plexripper HOT 7 CLOSED

Those are horrible to debug. 😩 PlexRipper writes its files to the Config/Logs directory, any chance you could get those?

from plexripper.

Those are horrible to debug. 😩 PlexRipper writes its files to the Config/Logs directory, any chance you could get those?

Let me try. Getting into the docker files on synology is something I'm not certain about. I'll see how I can do this.

from plexripper.

@JasonLandbridge - I mapped /Config/Logs and am waiting for it to crash again. It looks like it worked since a log of todays date was generated. So I guess I just need to wait for a crash again.

from plexripper.

Ah great! Thanks!

from plexripper.

@JasonLandbridge - Maybe this is related. I downloaded 1 movie that was around 8 GB. Hours later, the container is still holding onto almost 5 GB of memory. Why isn't this being released? I think this could be improved upon. It will just continue to eat more memory until it runs out and then weird things happen. Once I restarted the container, it went back to using 209 MB of memory idle.

from plexripper.

I have the same issue, my Container fills up until he`s restarting by OOM Issues.

from plexripper.

I think I have fixed this issue now, the problem was indeed memory not being properly released when downloading and merging files.

A new release (0.10.0-RC-1) is available now on both the latest and dev docker channels, which contains all the changes/fixes from the past several months. Let me know if this fixes the issues.

from plexripper.