Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b9
2018.1.0b10
Issue ID
1016815
Regression
Yes
Unity crash on [InitializeOnLoad] when opening project
How to reproduce:
1. Open given Unity project
2. If Unity doesn't crash
2.1. Close the project
2.2. Delete the Library
2.3 Open given Unity project
Expected result: Unity should not crash when [InitOnLoad]
Actual result: Unity should not crash
Regression first introduced in: 2018.1.0b9
Reproducible with: 2018.2.0a6, 2018.1.0b12
Not reproducible with: 2017.4.0f1, 2017.3.2f1, 2017.2.2p2, 2017.1.3p2, 5.6.5f3
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [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
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team