Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.0a2
2017.4.0f1
Issue ID
1017841
Regression
Yes
FatalError on MonoManager (NULL) when existing Unity with a specific dynamic library asset
To reproduce:
1. Open attached project
2. Press X to exit the Editor
3. When fatal error window appears press Quit
Expected results: Unity does not crash when the editor is closed.
Actual results: Unity crash after closing editor.
Reproduced in: 2017.3.0f3; 2017.3.2f1; 2017.4.0f1; 2017.4.1f1; 2018.1.0b13; 2018.2.0a7
Note: Before crashing Fatal error window appears: GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)
Note: Even in the new project, if you download and import the asset and exit the editor it crashes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment