Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.3.0b3

6000.4.0a1

6000.5.0a1

Issue ID

UUM-119900

Regression

No

[Linux] Crash on TerrainManager::CullAllTerrains when opening the "Terrain Shaders" Sample Scene

Terrain

-

Reproduction steps:
1. Create a new HDRP project
2. Open the Package Manager window (Window > Package Manager)
3. Select the Shader Graph package
4. Under “Samples” tab, import the “Terrain Shaders” Sample
5. Open the “Samples/Shader Graph/<version>/Terrain Shaders/Scenes/TerrainHDRP” Scene

Expected result: Scene is opened up
Actual result: The Editor crashes

Reproducible with: 6000.3.a6, 6000.3.0b3, 6000.4.0a1
Couldn’t test with: 6000.0.58f1, 6000.2.6f1, 6000.3.0a5 - Terrain Shaders are not available

Reproducible on: Ubuntu 25.04, Ubuntu 24.04, Fedora 41 (user)
Not reproducible on: Windows 11

First lines of the stack trace:
#2 0x005652e8489d7c in TerrainManager::CullAllTerrains(ScriptableCullingParameters const&)
#3 0x005652e797c9ce in CullScriptable(ScriptableRenderContext const&, ScriptableCullingParameters const&, ScriptableCullingAdditionalParameters const)
#4 0x005652e72c28d3 in ScriptableRenderContext_CUSTOM_Internal_Cull(ScriptableCullingParameters&, ScriptableRenderContextManaged const&, void
)
#5 0x00000040e764ea in (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull_Injected (UnityEngine.Rendering.ScriptableCullingParameters&,UnityEngine.Rendering.ScriptableRenderContext&,intptr)
#6 0x00000040e7646f in UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull (UnityEngine.Rendering.ScriptableCullingParameters&,UnityEngine.Rendering.ScriptableRenderContext,intptr)

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.5.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.