Search Issue Tracker
By Design
Votes
1
Found in
2021.3.50f1
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
Issue ID
UUM-101790
Regression
No
Editor crashes with "GetManagerFromContext: pointer to object of manager 'PlayerSettings' is NULL (table index 0)" error when launching a project with a corrupted library
Steps to reproduce:
1. Open the “user’s attached project”
2. Observe the "{{GetManagerFromContext: pointer to object of manager 'PlayerSettings' is NULL (table index 0)}}" error and the Editor crash
Reproducible with versions: 2021.3.50f1, 2022.1.0a1, 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: macOS 15.1.1 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environment tested
First few lines of StackTrace:
{noformat}0x00007FFB72C6AB6A (KERNELBASE) RaiseException
0x00007FF755C2B5AE (Unity) LaunchBugReporter
0x00007FF7555E91FB (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF7555E9ADD (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF7562AD47F (Unity) DebugStringToFilePostprocessedStacktrace{noformat}
Note: Editor still crashes after rebuilding the corrupted library when it is detected, or deleting the Library folder manually and opening the Editor
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
The error happens because the QualitySettings.asset file (inside the ProjectSettings/ folder) has been renamed to be "ProjectSettings.asset".
The ProjectSettings.asset asset should contain a "PlayerSettings" object and not a "QualitySettings" object. As such, when the system tries to load up the file, it fails.
Deleting the "ProjectSettings/ProjectSettings.asset" file will force Unity to create a new one. Alternatively, copying an existing one from another project (assuming it doesn't have the same issue) should also fix the particular issue.