Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-62786
Regression
No
"taskkill" command is ignored when the Player is running in Batch mode with Graphics API Vulkan
How to reproduce:
1. Open the “vulkan_repro“ project
2. Navigate to File → Build Settings and press “Build“
3. Open a cmd in the Build folder
4. In the cmd enter “KillMe.exe -batchmode“
5. Then enter “taskkill /im KillMe.exe“
6. Open Task Manager and expand the “Windows Command Processor“ process
7. Observe the processes
Expected result: KillMe.exe process is not running
Actual result: KillMe.exe process is running
Reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Notes:
- Running the command “taskkill /im KillMe.exe“ the second time will kill the process successfully
- Only reproducible if in Batch mode
- Not reproducible when building with Direct3D11 and Direct3D12
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Postpone, U7 ports.