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
- [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