Search Issue Tracker
Fixed
Fixed in 2021.3.26f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a11
Votes
2
Found in
2020.3.46f1
2021.3.17f1
2022.2.13f1
2023.1.0b10
2023.2.0a8
Issue ID
UUM-26444
Regression
No
A Player sometimes freezes and crashes when Graphic Jobs are enabled
How to reproduce:
1. Open the attached “repro-project”
2. Edit → Project Settings → Player and enable Graphic Jobs
3. Build the project
4. After opening the built project press “Enter park”
5. After the first tutorial introductions open the contracts panel in the upper right
6. Perform the tasks in the contracts panel
7. When the instructor finishes talking press Space to pause the game
8. Open the first option in the left menu (Build paths) and move the mouse a bit on the map
9. Open the fourth option in the left menu (Buid buildings) and quickly build buildings switching between categories (food, utilities, etc.) and place them on the map
Expected result: The Player runs without any issues.
Actual result: The Player freezes and crashes around 75% of the time.
Reproducible with: 2021.3.17f1
Could not test with: 2020.3.44f1, 2022.2.3f1, 2023.1.0b1 (Errors in the console, missing textures, ECS issues)
Reproducible on: Windows 10, macOS 12.2.1 (M1 Max)
Note: On macOS, the Player crashes instantly.
Comments (3)
-
stfunity
Aug 21, 2024 19:34
Still have this issue in 2023.2.20
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 (fix version 2023.2.0a11):
Fix landed in 2023.2.0a11