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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment