StephanFr

In the spirit of trying to get to the bottom of the leak which is where this started, what I have seen - in at least my case - is that memory gets allocated to Cura over time as the monitor runs but if you either minimize Cura or switch to the Prepare view, the memory slowly gets moved over to 'MemCompression'. It does not actually get released back to the system but it no longer is charged to Cura. Mem Compression shows up in RAMMap but not in the task manager. My suspicion is that there is leakage probably associated with the video stream and as this memory sits quietly after being leaked, it is scavenged by the MemCompression service and then get charged to that service and not Cura. If I start a print with Cura and switch back to the monitor, then the memory moves back to Cura from MemCompression.

I am seeing the same with 3.5 beta on Win 10 and I am using the Octoprint plugin. It is not clear to me where the memory is leaking, but TaskManager does not show memory reserved for Cura. That stays modest around 250 to 300MB in my case but my 8GB system runs out of memory after a couple days. The total in TaskManager goes over 90%, Cura shows maybe 300MB but when I exit Cura, the total memory in use drops from 90% back down to 30ish %. Given the above behavior, perhaps there is a leak associated with a driver and memory is getting allocated at the system level but not charged to the Cura process. I'll load RAMMap and try to get more data if that would help. Thanks, Stephan