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
- 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
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
- [UVCS] Popups in permissions window are sent behind the permissions view.
Add comment