Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
Issue ID
1104680
Regression
No
[Oculus GO] Using GPU Instancing takes excessive time to load shaders when calling Warmup() on Shader Variant Collection
To reproduce:
1. Build attached project "Instance Leak Files.zip" to Oculus GO
2. While in built app, press Button One on Oculus controller
3. Observe the screen and Logcat output
Expected: Shader WarmUp() takes excessive time to warm up (~45 seconds)
Actual: Shader WarmUp() takes several seconds to load at max
Reproduced in: 2018.2.20f1
Not reproduced in: 2018.3.3f1, 2019.1.0b1, 2019.2.0a3
Note1: issue is also reportedly consuming sizeable amounts of memory
Note2: does not reproduce if GPU instancing is disabled
Note3; project freezes on launch in 2017.4.19f1, likely an issue of backwards incompatibility
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment