Search Issue Tracker
Fixed
Fixed in 6000.0.57f1, 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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note (fix version 6000.3.0a1):
Address job lifetime warnings when GraphicsStateCollection warmup spans many frames