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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment