Search Issue Tracker
By Design
Votes
1
Found in
2018.3.0a1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1147963
Regression
No
[IL2CPP] Player crashes on closing it if System.Threading.Thread is running
Steps to reproduce:
1. Download 1147963_repro.zip
2. Build project for Standalone platform (IL2CPP backend)
3. Launch player
4. Press the exit button
Results: Player freezes/crashes when exiting if the thread is running.
Reproduced with: 2019.3.0a1, 2019.2.0a13, 2019.1.0f2, 2018.3.13f1
Note:
- not reproducible with mono backend
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Managed code threads should exit when the application exits. Something in the application needs to indicate to those threads that they should exit. The .NET runtime (IL2CPP in this case) it only allowed to kill background threads. The threads in this project are not background threads.