Search Issue Tracker
Fixed in 2020.3.46f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0b9, 2023.2.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.4f1
2023.1.0b1
Issue ID
UUM-24705
Regression
No
[Linux] Editor ignores SIGTERM signal when using command 'kill <PID>'
Reproduction steps:
1. Create a new 3D project
2. Open the Terminal
3. Enter this command: ps aux | grep 2021.3.14f1 | grep -v grep | awk '{print $2}'
4. Enter this command: kill <first PID from the results of the previous command>
Expected result: Unity Editor is killed
Actual result: Unity Editor is still open
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.4f1, 2023.1.0b1
Reproducible on: Ubuntu 20.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Add comment