Search Issue Tracker
Active
Under Consideration for 6000.6.X
Fixed in 6000.3.13f1, 6000.5.0a7
Votes
0
Found in
6000.3.6f1
6000.4.0f1
6000.5.0a8
6000.6.0a2
Issue ID
UUM-137390
Regression
No
Crash in RenderGraph Bloom following upgrade to Unity 6.3.6
100% repro crash after around 30min, following upgrade to Unity 6.3.6.
If we disable Bloom on our Volume Profile, the issue seems to go away,
IndexOutOfRangeException: Index was outside the bounds of the array.
_at UnityEngine.Rendering.DynamicArray`1[T].get_Item (System.Int32 index) [0x00018] in .\Library\PackageCache\com.unity.render-pipelines.core@9a9c0155552c\Runtime\Common\DynamicArray.cs:367_
at UnityEngine.Rendering.RenderGraphModule.RenderGraphResourceRegistry.GetTextureResource (UnityEngine.Rendering.RenderGraphModule.ResourceHandle& handle) [0x00023] in .\Library\PackageCache\com.unity.render-pipelines.core@9a9c0155552c\Runtime\RenderGraph\RenderGraphResourceRegistry.cs:827
at UnityEngine.Rendering.RenderGraphModule.RenderGraphResourceRegistry.GetTexture (UnityEngine.Rendering.RenderGraphModule.TextureHandle& handle) [0x00019] in .\Library\PackageCache\com.unity.render-pipelines.core@9a9c0155552c\Runtime\RenderGraph\RenderGraphResourceRegistry.cs:189
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.5.0a7):
The issue is fixed in Unity 6000.5 because of other code changes with Bloom / Rendergraph, so there is no need to backport
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1