Search Issue Tracker
Won't Fix
Votes
0
Found in
4.5.0f6
Issue ID
610288
Regression
Yes
Shader compiler hangs on 4.5 in SpaceGraphicsToolkit package shaders
Shader compilers run out of memory in some shaders of SpaceGraphicsToolkit package. Seemingly a regression in 4.5.x; worked in 4.3.
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Aras
Sep 05, 2014 10:11
So in 4.5 we made Cg shader compiler report errors on correct line numbers by changing the way shader #includes are processed. However, this particular set of shaders has really convoluted way of #includes, that somehow makes Cg go into "leak a ton of memory!" mode outside of our control.
I'm afraid there's not much we can do here :(
Good thing is, in 5.0 we mostly got rid of Cg, so things should be better.