Search Issue Tracker
Not Reproducible
Votes
9
Found in
2018.4
2019.4
2020.3
2020.3.0f1
2021.1
2021.2
Issue ID
1322199
Regression
No
Running too many instances of the standalone player causes new ones to crash
How to reproduce:
1. Create and build a new project for Windows or Linux
2. Download and open the attached "run.py" script
3. Modify the 5th line providing the path to the built project's executable
4. Run the python script and observe the crash
Reproducible with: 2018.4.33f1, 2019.4.22f1, 2020.3.1f1, 2021.1.0f1, 2021.2.0a10
Notes:
1. Reproducible on Ubuntu 18.04 and Windows 10
2. On Ubuntu 18.04 it may take several attempts to get the crash to occur
3. The number of open players on Linux can be as high as 200 and 30 on Windows for the crash to reproduce
4. The exit codes thrown upon crashing usually are -11, -6, 1, or 3221225477 (on Windows 10 only)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment