Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0b22
Issue ID
809029
Regression
No
Initializing global MonoBehaviour using new keyword causes Unity to crash
Reproduction steps:
1. Open user attached project "Main" scene.
Notice Unity is crashing
2. Comment Line 14 in CloudGen.cs script which initializes new PlayerManager() (which is also a MonoBehaviour)
3. Reopen user attached project "Main" scene.
Unity should be running fine.
Reproduced on: 5.3.5p6, 5.4.0b22, 5.4.0b24
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
- Crash on OnDemandScheduler::HandleImportWorkerLogs when performing various Unity operations
Add comment