Search Issue Tracker
Fixed
Fixed in 6000.4.11f1, 6000.5.0b12, 6000.6.0a7
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, macOS
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
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a7
Resolution Note (fix version 6000.6.0a7):
Fixed in 6000.6.0a7