Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.13f1
2021.2
2022.1
Issue ID
1376434
Regression
No
Server build doesn't respond to "Ctrl+C" after setting "Console.ForegroundColor"
How to reproduce:
1. Open the user attached project (svrbuild-ctrl-c.zip)
2. Press Ctrl+Shift+B to open the "Build Settings" window
3. Make sure "Server Build" is enabled and build the project
4. Open the terminal
5. Navigate to the build directory and run the build from the terminal
6. Once it starts press Ctrl+C to terminate the program
Expected result: the build terminates
Actual result: the build doesn't react to Ctrl+C being pressed
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a13
Notes:
1. Reproducible on Ubuntu 20.04 and OSX (As reported by the user)
2. Not reproducible on Windows 10
3. The build keeps running after the terminal is closed so to stop it when Ctrl+C doesn't work the system's task manager has to be used to kill the process
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
- Crash on RaiseException when AddGameElement handles a generic type
- Interpolation 2D results are inconsistent when position.z = position.x is called on Late Update
- Game View's scale slider bar gets set to 2.5x when entering Play Mode
- Crash/Memory leak in a WebGL build when executing a very large switch statement multiple times
- [Asset Bundles] The Active Build Platform is being used instead of the build target to determine material/shader compilation
Resolution Note (fix version 2021.2):
Patch has been applied to the Unity fork of Mono to disable Mono handling SIGINT when running with Unity or the player. This allows the Unity code to handle SIGINT.
https://github.com/Unity-Technologies/mono/pull/1546
Fixed in 2022.2.0a7
Resolution Note (fix version 2022.1):
Fixed in 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.4f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.35f1