Search Issue Tracker
In Progress
Fix In Review for 6000.0.57f1
Fixed in 6000.2.2f1, 6000.3.0a1
Votes
0
Found in
6000.0.40f1
6000.3.0a1
Issue ID
UUM-102639
Regression
No
Warnings when warming up shaders with GraphicsStateCollection
Warnings when warming up shaders with GraphicsStateCollection
A team are using GraphicsStateCollection API for warming up our shaders. It works well, but when we warm up shaders, it spams several instances of this warning:
Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 15)
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
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
- Broken compute shaders propagate via the cache server
Resolution Note (fix version 6000.3.0a1):
Address job lifetime warnings when GraphicsStateCollection warmup spans many frames