Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Drawables memory leak

See original GitHub issue

Edit:

updated to Magick.NET-Q16-AnyCPU 7.7.0
update VS Code to 1.27.1

Description

I’m running a code over a bunch of images on my computer. I’m resizing 1024x768 images to 512x512. I need to add black borders (because of aspect ratio mismatch) to the 512x512 image. This is why I’m using Drawables class. Here is a snippet that runs over every single image:

            using (MagickImage image = new MagickImage(_inPath, 1024, 768))
            {
                image.Sample(512, 384);

                using (MagickImage result = new MagickImage(MagickColors.Black, 512, 512))
                {
                    result.Quality = 50;
                    
                    //this causes a leak
                    new Drawables()
                    .Composite(0, (512 - 384) / 2, image)
                    .Draw(result);

                    result.Write(_outPath);
                }
            }

I’m looking at the Task Manager while the program is running. Every 10-20 processed image adds about 10mb of RAM to the memory. I have about 10 000 images to go through. After the RAM usage reaches about 2GB the execution slows down drastically. If I stop the program and start it again from the point it stopped running the last time, it again runs at initial speed.

Now if I comment the new Drawables().Coposite().Draw() line and run again, nothing is being added to the memory. The Drawables class does not have a .Dispose() method. So I’m at a bit of a loss here.

Environment: