Memory Leak

[twilliams1012]

Would it appear that there is a memory leak?

Before creation:79360 After creation:139296 Object is null True After null:139352 Before creation:125224 After creation:139976 Object is null True After null:139720 Before creation:125592 After creation:140056 Object is null True After null:139800

[mthamil]

I suppose it's possible. Do you have any more information?

[twilliams1012]

I noticed when constructing a IFlatFileEngine via the Factory memory continues to hang around. I'm trying to use the engine inside an API and notice every time the endpoint is called memory continues to rise. Below is a copy of the console application I've used for testing.

    static void Main(string[] args)
    {
        MonitorMemoryUsage();
        MonitorMemoryUsage();
        MonitorMemoryUsage();

        Console.WriteLine("Press any key to exit.");
        Console.ReadKey();
    }

  
    private static void MonitorMemoryUsage()
    {
        Configuration.Converters.UseOptimizedConverters();

        DisplayMemoryAfterGc("Before creation");

        var fluentEngine = new FixedLengthFileEngineFactory()
                .GetEngine(new FixedSampleRecordLayout());
     
        DisplayMemoryAfterGc("After creation");

        if (fluentEngine != null)
        {
            fluentEngine = null;
        }

        Console.WriteLine($"Object is null { fluentEngine == null }");
        DisplayMemoryAfterGc("After null");
    }

    private static void DisplayMemoryAfterGc(string eventType)
    {
        GC.Collect();
        GC.WaitForFullGCComplete();
        var totalMemory = GC.GetTotalMemory(true);
        Console.WriteLine(eventType + ":" + totalMemory);
    }

[twilliams1012]

It appears it may not be a memory leak but what looks like a leak caused by lambdas. I'm curious if the Func<object, object?> _getValue and Action<object, object?> _setValue are being generated as static members and cannot be collected by GC.

[mthamil]

Hm, it is certainly possible something is being captured by a lambda and held on to. I will look into it. I very much appreciate your help.