Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3
2020.3.4f1
Issue ID
1330724
Regression
No
[Enlighten] Server build starts Enlighten worker threads during shutdown
Steps to reproduce:
1. Create a new Unity project
2. Open Build Settings
3. Check the 'Server Build' option
4. Build and Run the project
5. Press CTRL + C
6. Notice that for a brief period, multiple Enlighten worker threads are shown in the Command Prompt window
Notes:
- Command Prompt output looks like this (number of threads depends on the processor):
Setting up int worker threads for Enlighten.
Thread -> id: [HASH] -> priority: 1
Thread -> id: [HASH] -> priority: 1
Thread -> id: [HASH] -> priority: 1
Thread -> id: [HASH] -> priority: 1
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (2021.2.X):
The Enlighten worker threads are created once the engine is shutting down. During normal execution they are not running.