Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
4
Found in
5.6.1f1
Issue ID
994408
Regression
No
It is possible to bypass Force Single Instance
To reproduce:
1. Create a new project and build it
2. Select the .exe file and double tap Enter quickly (might require multiple tries)
Expected: opening the build multiple times in a quick succession when Force Single Instance is on, opens only one instance and shows errors if another one is trying to be opened
Reproduced in 5.6.1f1, 5.6.5f1, 2017.1.3p1, 2017.2.1p3, 2017.3.0p4, 2018.1.0b5
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
- “[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
Peter77
Aug 11, 2018 04:52
Fixed in Unity 2017.4.9f1
https://unity3d.com/unity/whatsnew/unity-2017.4.9
AlanMattano
Feb 08, 2018 03:17
Workaround link?