Huge peak memory consumption while displaying images

[lisindima]

Summary and/or background The moment I open my list with a large number of images, there is a huge peak in memory consumption. Sometimes this does not happen in the same situation, I could not understand this pattern. I also notice this problem in your demo application for this package. When I choose the option with the largest images.

OS and what device you are using

• OS: 14.2 RC (18B91)
• Device: Simulator and iPhone 11 Pro

Version of URLImage library

• 2.1.2
• [X] The bug is reproducible in the latest version.

What you expected would happen Don't have such terrible memory consumption

What actually happens Peak memory consumption, which causes a crash on a real device due to insufficient memory.

Sample code

URLImage(
            url: path,
            options: URLImageOptions(cachePolicy: .returnCacheElseLoad(cacheDelay: nil, downloadDelay: delay)),
            inProgress: { progress in
                ProgressView(value: progress)
                    .progressViewStyle(CircularProgressViewStyle())
            },
            failure: { _, retry in
                Button(action: retry) {
                    Image(systemName: "arrow.clockwise.circle.fill")
                        .imageScale(.large)
                }
            }
        ) { image in
            image
                .resizable()
        }
        .cornerRadius(8)
        .frame(width: size, height: size)

Test data This is reproduced with any images with a resolution greater than 1000x1000 and a weight greater than 1MB.

Additional information:

• [X] Screenshots or video demonstrating a bug;
• [ ] Crash log;

[dmytro-anokhin]

Memory spikes happen naturally because images are big, this is not necessarily a bug. However, version 2 is missing control over maximum size of a decoded image. Adding this will help reduce memory consumption. I'm working on it.

[dmytro-anokhin]

And thank you for detailed report 👍

[dmytro-anokhin]

Hey,

there's a new version 2.1.4. You can now specify maximum image dimensions in pixels using maxPixelSize property of URLImageOptions. It defaults to 300x300. I picked this number randomly, maybe will change it or introduce some logic based on the device type in the future.

Using maxPixelSize eliminates memory spikes in my tests. I'm closing the issue, but feel free to reopen if you discover an edge case.