Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.1f1
Issue ID
840507
Regression
Yes
"Too many threads" error and crash when executing procedural terrain generation
Reproduction steps:
1. Open attached project (TooManyThreads.zip)
2. Open "TerrainGeneratopmTest" scene (in Scenes folder)
3. Drag and drop "StartupScreen" scene to Hierarchy
4. Click Play
Expected result:
No crash
Actual result:
Too many threads error dialog is thrown and Unity crashes (see Error.png attached)
Reproduced with: 5.3.5f1, 5.4.1f1, 5.4.3f1, 5.5.0b11, 5.5.0f1, 5.6.0a3
Not reproducible: 5.2.5f1, 5.3.4f1
Regression introduced in 5.3.5f1
----------------------------------------------
There's an internal upper limit of maximum number of concurrent threads (2048 or so). Need to use smth like thread pooling to address the issue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment