Search Issue Tracker
Fixed in 7.4.0
Votes
0
Found in [Package]
7.2.1
Issue ID
1227490
Regression
Yes
VolumeComponent allocates memory every frame in Standalone builds.
Expected:
VolumeManager should not allocate memory everyframe.
Result:
VolumeParameter.GetHashCode allocs memory.
Issue only reproduces in standalone player. Editor is fine.
How to reproduce:
- Open URP GraphicsTestScene.
- Build Project containing scene 104 BokehDepthOfField
- Build with Deep Profiling enabled.
- Check profiler, see that VolumeParameter.GetHashCode is allocating memory.
This is a regression in URP with PPv3.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note (fix version 7.4.0):
Fixed in https://github.com/Unity-Technologies/ScriptableRenderPipeline/pull/6228