Search Issue Tracker
Fixed in Unity 2018.2
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
- Absolute paths from included packages cannot be converted to virtual paths in Assets/Packages
- Crash in VCProvider when upgrading project from 18.3 to 19.1 and 19.2
- Android Vulkan corrupted rendering when there is no camera in the scene
- Creating mesh assets produces broken blendshapes
- Array.BinarySearch parameters get swapped from .NET 3.4 to .NET 4.0
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?