In our case a heavy memory leak occurs once you open the Scene view while using VR:
2 cameras are rendering. One to Oculus or open VR, one to screen. Then RAM fills up with about 2GB/Second so it's really unusable. If we disable VR everything works fine.

Reproducible on: 2023.3.0a3, 2022.3.8f1
Not reproducible: 2021.2.7f1

This might be related with this bug which has been fixed: https://issuetracker.unity3d.com/issues/editor-performance-drops-as-oculusruntime-dot-waittobeginframe-time-ms-increases-to-150-200-ms-in-play-mode-when-msaa-is-enabled-and-scene-view-is-opened-slash-focused

I'm amazed that this still hasn't been resolved.

This problem also exists when previewing models and animations with imported models. Mucking about with the preview window causes heaps of allocations until your OS necks itself.

Is there any way to bypass this problem?

Hi,

Any update? I have been waiting for a few months for the correction and I have my project to send ASAP...

Thanks in advance
Jérémy

This issue needs fixing ASAP!

Unfortunately, at this point, I'm not sure Unity knows how to fix this issue just yet.

I have inquired about the fix several times since, the fix was supposedly on it's way and have received no update.

Perhaps getting some additional attention on the thread linked below will help get the ball rolling.

https://forum.unity.com/threads/unity-2022-3-2f1-urp-render-texture-from-camera-is-crashing-the-application.1453870/

Vote guys, one day in the next 5 years they'll solve accidentally on a next version.
This is issue is so old, why doesn't they care about bugs ?

Just wanted to give an update for anyone having this issue: while still unsolved I've managed to clean my corrupted project by deleting the library file and other temp files from the repository and then on the editor package manager uninstalled and reinstalled URP. After that I've finally gotten rid of the 'ghost' render texture allocation (92.4 MB in Unity Objects Allocations). Another very important tip: Always use version control.. always if possible. I thought I wouldn't need it since I was working on a quick gameplay prototype but that was a mistake.

2022.3.3f1 LTS. This issue not only resulted in a memory leak but now the memory profiler (and Xcode memory profiling as well) always show that the render texture is taking 90 Mb of memory space. EVEN AFTER I have deleted the multi-camera scene and the render texture asset. It appears that the generated maps are still lurking somewhere in the project. I have tried making a clean build, uninstalling and reinstalling URP, and other tricks to no avail.

It's honestly frustrating. Its looks like the only way forward is to start with a new clean project...........