Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.33f1
2022.3.16f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
Issue ID
UUM-59236
Regression
No
Crash on RaiseException and GetManagerFromContext error thrown when opening a project
Reproduction steps:
1. Open the attached “Control_Anim.zip” project
2. Observe the crash
Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0b1
Reproducible on: macOS Sonoma 14.0 (Intel), Windows 11 (by the reporter)
Not reproducible on: no other environment tested
First few stack frames:
{{0x00007FFE5855567C (KERNELBASE) RaiseException
0x00007FF703C926EE (Unity) LaunchBugReporter
0x00007FF70365DFAB (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF70365E88D (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF704315FEF (Unity) DebugStringToFilePostprocessedStacktrace}}
Note: Error thrown when opening the project - “{{GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)}}"
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.