Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2018.3.0a1
2019.3
2019.3.0a4
2020.2
Issue ID
1223636
Regression
Yes
PVRContextManager Thread has no data and occupies important area in Profiler Timeline View
How to reproduce:
1. Create a new project
2. Enter Play Mode -> Pause the Play Mode
3. Open Profiler Window -> Open Timeline View
Expected result: Main Thread, Render Thread, Job, Loading, Scripting Threads are shown first
Actual result: PVRContextManager thread has no data and is between Main Thread and Render Thread (which prevents users from seeing an important Job system loading content)
Reproducible with: 2019.3.0a4, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1
Not reproducible with: 2017.37f1, 2018.4.18f1, 2019.3.0a3
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a4
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b4
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.9f1