Search Issue Tracker
Won't Fix
Fixed in 2022.3.7f1, 2023.1.7f1, 2023.2.0b2, 2023.3.0a1
Votes
3
Found in
2022.3.5f1
2023.1.0b12
2023.2.0a10
2023.3.0a1
Issue ID
UUM-33301
Regression
Yes
[Frame Debugger] Crash on keywords::LocalSpace::Find when opening Frame debugger with a compute shader in the scene
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Enter The Play Mode
3. Open the Frame Debugger (Window > Analysis > FrameDebugger)
4. Click the “Enable“ button
Expected result: Frame debugger is enabled
Actual result: Editor crashes
Reproducible with: 2022.2.0b12, 2022.2.16f1, 2023.1.0b12, 2023.2.0a10
Not reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.0b11
Reproducible on: Windows 10
First few lines of stack trace:
{noformat}0x00007ff754053ccf (Unity) keywords::LocalSpace::Find
0x00007ff753f74d27 (Unity) FrameDebugger::AddKeywordsToFrameDebuggerData
0x00007ff753f7fbb7 (Unity) FrameDebugger::SetNextShaderKeywords
0x00007ff754005ab3 (Unity) ComputeShader::BeforeDispatch
0x00007ff754009080 (Unity) ComputeShader::DispatchComputeShader{noformat}
Comments (1)
-
dwb_unity
Jul 18, 2023 18:10
I worked around this by avoiding use of multicompile and instead mapping each kernel to a single define.
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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
Resolution Note:
Already solved