Steps to reproduce:
- Open the attached project
- In the Profiler window, switch to Edit mode
- Focus Profiler's Memory section and observe the allocated memory size
- In the Frame Debugger window, press the Enable button
- Observe the allocated memory size again
Actual results: Frame debugger uses excessively large amounts of memory, causing slowdowns or potential crashes. Especially with HDRP and high Game view resolutions
Expected results: Frame debugger causes more memory to be allocated, but the additional amount does not cause significant slowdowns or crashes in reasonable settings
Reproducible with versions: 6000.3.4f1, 6000.3.13f1, 6000.4.2f1, 6000.5.0b3, 6000.6.0a2
Not reproducible with versions: 6000.0.71f1, 6000.3.3f1
Tested on (OS): macOS 26.3.1, Windows 11
Notes:
- Metrics of in use memory after enabling Frame Debugger on MacBook Pro (M1 Max) with Game view set at 4K resolution
- 6000.3.3f1
- HDRP ~ 6.12GB
- URP ~ 4.27GB
- 6000.3.4f1
- HDRP ~ 18.47GB
- URP ~ 5.97GB
- 6000.6.0a2
- HDRP ~ 20.58GB
- URP ~ 8.19GB