Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Won't Fix in 2018.1.X
Votes
0
Found in
2017.3.0f3
Issue ID
1005502
Regression
No
Unity crashes when MonoImporter.SetExecutionOrder is called from RuntimeInitializeOnLoadMethod
How to reproduce:
1. Open given Unity project
2. Enter "Title" scene
3. Enter Play Mode
4. Unity crashes
Reproducible with: 2018.2.0a1, 2018.1.0b9, 2017.3.1p2, 2017.2.2f1, 2017.1.3p1, 5.6.5p2
Note:
In script called "Root" 20 line ( UnityEditor.MonoImporter.SetExecutionOrder(monoScript, -32000)) is crashing only when it's in RuntimeInitializeOnLoadMethod (line 8)
Verified fixed in 2018.3.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Element name is not updated when clicking on a different element after entering name in the Inspector
- Crash on Texture::TextureIDMapInsert when opening a specific project
- Null reference exceptions occur when ScriptableObjects saved in the same .asset file are referenced in runtime
- Depth texture is flipped when specific URP rendering settings are applied
- Warning of an unknown Script missing is logged when selecting VFX in Play Mode
Add comment