Search Issue Tracker
Fixed
Fixed in 6000.0.61f1, 6000.2.9f1, 6000.3.0a2
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0a1
Issue ID
UUM-108846
Regression
Yes
Per-frame GC Allocation when using HDRP Lens Flare Post Process Effect
How to reproduce:
- Create and open a new 3D HDRP Sample Template
- Open Profiler (Window → Analysis → Profiler)
- Enable Deep Profile and Call Stack in the Profiler
- Enter Play Mode
- Record, and then press on any frame in the Profiler
- Search for GC.Alloc in searchbar
- Select any GC.Alloc in the Hierarchy
- Change ‘No Details’ to 'Calls' in the Profiler
- Observe the 'Calls From' section in the Profiler
Expected result: No GC.Alloc calls are made by ‘HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass()'
Actual result: One of the GC.Alloc calls are made by 'HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass()’
Reproducible in: 2023.3.0b1, 6000.0.60f1, 6000.2.8f1, 6000.3.0a1
Not reproducible in: 2023.3.0a19
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: The Call allocates ~152 B each frame
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Add comment