Search Issue Tracker
Fixed in 2021.3.49f1
Fixed in 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.2.0a1, future release
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.11f1
2023.3.0b8
6000.0.0b11
6000.1.0a7
6000.2.0a1
Issue ID
UUM-64442
Regression
No
Crash on StackWalker::GetCurrentCallstack when opening a specific project
How to reproduce:
1. Open the “IN-68740_repro“ project
Expected result: The project opens
Actual result: The Editor crashes
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of Stack Trace:
0x00007ff64562cabd (Unity) StackWalker::GetCurrentCallstack
0x00007ff645631b89 (Unity) StackWalker::ShowCallstack
0x00007ff6466053c1 (Unity) GetStacktrace
0x00007ff645630fd6 (Unity) winutils::PrintStackTrace
0x00007ff64562c2ec (Unity) winutils::CrashHandler::DefaultSignalHandler
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment