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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This seems to be a driver issue. We do not support this unique setup.