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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment