Memory leak in DCS about duetsoftwareframework HOT 6 CLOSED

I suspect this is related to anonymous JSON deserialization in the DCS status update thread and a problem caused by the JSON.NET library. Can you check if the problem persists with the latest DSF version?

That particular code is still temporary and will be replaced soon, but I already added some further improvements to that part of the latest DCS version.

from duetsoftwareframework.

I'll tell you tomorrow. ;-)

from duetsoftwareframework.

It seems that whatever you did made it worse. The additional memory consumption was increased to 90-100MiB/hour but does not seem to be linear anymore (according to my few datapoints so far). I will collect some more data throughout the next days.

from duetsoftwareframework.

Could it be simply that DSF hasn't been given a memory limit, so as the memory is there the .NET subsystem is grabbing it in preference to doing garbage collection? I presume there is a way of setting a memory limit.

from duetsoftwareframework.

I don't know .NET Core enough to say how memory is limited. A quick search also did not reveal anything. I know from Java that if you do not specify anything it will be limited to 25% of total RAM but obviously that's not the case for .NET Core. I will try to find a setting if possible and check with a very low value if it
a) garbage collects and continuous or
b) dies with OutOfMemoryException

EDIT: I have now limited the amount of memory externally (since I did not find a switch for .NET Core) in multiple steps. It is not allowed to use any swap space at all. The low memory usage mark is set to 100MB, the high mark is set to 250MB and once it reaches 500MB it will be killed by the OS.

from duetsoftwareframework.

This is fixed in DCS 1.0.2.2.

from duetsoftwareframework.