Memory not freed

I put an Image on FRX, Request ‘TestReport’ multiple times,My container footprint is 1GB or higher. Is there a problem with my code?

[Route("/TestReport")]
        public string TestPrint(string type)
        {

            using Report report = new Report();
            report.Load("3.frx");

            using FileStream fs = new FileStream("1.png", FileMode.Open, FileAccess.Read);
            byte[] buffur = new byte[fs.Length];
            fs.Read(buffur, 0, (int)fs.Length);
            fs.Close();

            using ImageExport image = new ImageExport();
            image.ImageFormat = ImageExportFormat.Jpeg;
            image.Resolution = 300;

            var data = new List<object>() { new { Image = buffur } };
            report.RegisterData(data, "Test");
            report.Prepare();
            using MemoryStream reportImageStream = new MemoryStream();
            report.Export(image, reportImageStream);

            return Convert.ToBase64String(reportImageStream.ToArray());
        }

My Code

[ElBedeawi]

@Ramoshuai I tried the solution and it works fine the container memory went down to ~200MB

This is my current Dockerfile, may be it can be better but this is what worked with me.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
RUN apt-get update && apt-get install -y --allow-unauthenticated libc6-dev libgdiplus libx11-dev
RUN apt-get install -y libgif-dev autoconf libtool automake build-essential gettext libglib2.0-dev libcairo2-dev libtiff-dev libexif-dev libpango1.0-dev git
WORKDIR /var/customLib
RUN git clone https://github.com/mono/libgdiplus.git
WORKDIR /var/customLib/libgdiplus
RUN ./autogen.sh --with-pango --prefix=/usr
RUN make
RUN make install
WORKDIR /app
EXPOSE 80

[ElBedeawi]

Hi, we are experienceing the same behaviour with version 2022.2.12. This only happends in linux env, not in windows.

Can anyone confirm if @ElBedeawi solution works? Is it a problem with libgdiplus?

Regards

I haven’t tried the latest version yet, but for the version I’m using “2021.4.13” it was the issue and building it using that dockerfile worked fine for me.