Search Issue Tracker
Fixed in 2020.3.38f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a1
Votes
0
Found in
2022.1.3f1
2022.2.0a14
2023.1.0a1
Issue ID
UUM-607
Regression
Yes
[IL2CPP] Player hangs for 20 seconds after closing it when running threads
Reproduction steps:
1. Open the user's attached "SlowShutdown.zip" project
2. Go to Edit > Project Settings > Player > Other Settings > Configuration and make sure IL2CPP is set as Scripting Backend
3. Build and Run for PC, Mac & Linux Standalone
4. After the project is built and the Player opens, close it
Expected result: Player closes instantly
Actual result: Player hangs and closes after 20 seconds
Reproducible with: 2021.1.0a8, 2021.3.3f1, 2022.1.1f1, 2022.2.0a14
Not reproducible with: 2019.4.39f1, 2020.3.34f1, 2021.1.0a7
Not reproducible with: Mono Scripting Backend
Tested and reproduced with: Windows 10
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note (fix version 2020.3):
In 2020.3 the player didn't hang for 20 seconds, but has the same underlying issue. The issue is that IL2CPP leaks an internal thread object each time a thread is created. The shutdown code in 2021.2+ caused these leaked thread objects to slow the player close.
So this fix only cleans up that memory leak (which is relatively small).