Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
Issue ID
UUM-43570
Regression
No
The Player freezes when relaunching a build after it has been running for a couple of hours when using two GPUs and multiple display setup
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/Startup.unity” Scene
3. Build and run the Player (File > Build And Run)
4. Wait for a couple of hours
5. Close the Player
6. Open the Player
Expected result: The Player is opened
Actual result: The Player freezes after displaying the Unity logo
Reproducible with: 2021.3.27f1
Reproducible on: Windows 10
Notes:
- We could not test the issue as we do not have that kind of setup
- Only reproducible on two GPUs and multiple display setups (5 or more)
- Not reproducible if the Player has been running for a short time
- After the reproduction steps were made, the built Player will always result in freeze, even if rebuilding
- Rebuilding with a different product name works as a workaround
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:
This seems to be a driver issue. We do not support this unique setup.