[Bug]: OOM issues when performing many image based resizes / operations

[rcky844]

What happened?

This bug might be related to many issues within the code base, such as not freeing memory after use. The most direct observation is a direct application crash and possible loss of data.

What I propose and have observed, which may lead to this issue:

• Object selection system may not be freeing memory properly
• Moving & resizing images may leave behind old renders in memory
• Removed image files are not deleted from the .bfly container file (fixed in c8a3367)
• Pasted and removed images from an active editing session is not freed

Version

2.5.0-beta.3

Platform

Linux

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[CodeDoctorDE]

I think i fixed all of them, can you try the latest 2.5 rc?

[rcky844]

I think i fixed all of them, can you try the latest 2.5 rc?

This might have introduced another bug, needs more testing.

[rcky844]

I believe most OOM issues have been resolved as of the stable release of 2.5, incl. long duration usage. Closing this for now.