Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
2022.3.75f1
6000.0.74f1
6000.3.14f1
6000.4.5f1
6000.5.0b6
6000.6.0a4
Issue ID
UUM-140945
Regression
No
Crash on StackWalker::GetCurrentCallstack when opening a project with specific project settings
How to reproduce:
1. Open the attached “IN-139954” project
2. Observe the crash
Reproducible with: 2022.3.3f1, 2022.3.75f1, 6000.0.74f1, 6000.3.14f1, 6000.4.5f1, 6000.5.0b6, 6000.6.0a4
Reproduced on: Windows 10 (user reported), Windows 11
Not reproduced on: No other environment tested
Note: The crash does not occur after deleting the projectsettings.asset in the Project Settings folder
First few lines of the stack trace:
0x00007ff70d689e7d (Unity) StackWalker::GetCurrentCallstack
0x00007ff70d68ef59 (Unity) StackWalker::ShowCallstack
0x00007ff70e64e361 (Unity) GetStacktrace
0x00007ff70d68e376 (Unity) winutils::PrintStackTrace
0x00007ff70d6896ac (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
- Graph Toolkit variables rarely get instantiated on the canvas on Ubuntu
- Visible edge smearing occurs on moving GameObjects when using TAA in HDRP
- NullReferenceException is thrown due to stale m_Ellipsis reference when swapping the font asset
- Crash on mono_add_process_object when exiting Play mode on a specific project
- Graph asset icons are corrupted on Ubuntu
Add comment