Potential Memory Leak with Disaster Recovery Plugin

Enabling the disaster recovery plugin causes a memory leak when importing and editing a large amount of textures. This can result in either a system lockup or a crash.

1. Create a 4.23 preview project and enable the disaster recovery plugin
2. Import a very large amount of textures, about 3GB worth
3. Select all the textures and bulk edit them via the property matrix
4. Change the texture compression to Normal Map

Results: Memory usage quickly ramps up until no system memory is free resulting in a system hard lock or Engine crash.

Expected: The changes to the textures to take effect without locking up the system.

How does TextureRenderTarget2D get TArray<uint8> type data?

How do I set a material as a post-processing material?

Why does the REMOVE method of map container remove elements have memory leaks?

How to delete some elements correctly when deleting an array loop?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

UMG RichText not appear image when packaged

How does TArray loop correctly remove elements in blueprints?

What is the difference between Camera and CineCamera?