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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
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?