Search Issue Tracker
Fixed in 5.3.0
Votes
1
Found in
5.1.2f1
Issue ID
725040
Regression
Yes
Force single instance crashes second instance of built game
Steps to reproduce:
1. Create new project
2. Check "Force Single Instance" in player settings
3. Build project
4. Run it
5. Run one more instance and notice that it crashes
Note: Prior to 5.1, error was returned that another game instance is already running
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
frikic
Jun 22, 2016 15:02
This was not fixed even in recent 5.2.5, that's really bad... so are we now forced to update to 5.3,
or could there be a patch to fix this annoying issue?
yoyo
Nov 16, 2015 17:17
Will this be back-ported to 5.2?