Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3.3f1
2020.1.0a24
2020.2
Issue ID
1225421
Regression
Yes
"Long Running Job detected" errors are thrown when Shader Variants / Materials are compiled in a Play Mode
How to reproduce:
1. Download the user's project
2. Before opening the project delete "ShaderCache" folder found in OceanBreeze->Library
3. Open the user's project
4. Enter Play Mode
5. Use "A" and "E" buttons to get into the purple trigger
Expected result: No errors are thrown
Actual result: "Long Running Job detected" errors are thrown
Reproducible with: 2019.3.3f1, 2020.1.0b3, 2020.2.0a4
Not reproducible with: 2019.3.2f1
Could not test with: 2017.4.38f1 because of missing Prefabs, 2018.4.20f1 because of namespace errors
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a7