Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.0a10
Votes
1
Found in
2022.3.62f1
6000.0.49f1
6000.1.4f1
6000.2.0b1
Issue ID
UUM-105458
Regression
No
SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
Reproduction steps:
1. Open the attached "test_disc.zip" project
2. Open the "Assets/OutdoorsScene.unity" Scene
3. Open the Profiler ("Window -> Analysis -> Profiler")
4. In the Profiler, turn on Deep Profile
5. Enter the Play Mode
6. After a few seconds, pause the Play Mode
7. In the Profiler, select the last frame (or second to last)
8. Search for "SystemInfo.get_graphicsDeviceName()" method
9. Observe the method's GC Alloc value
Expected result: The value is 0 B
Actual result: The value is around 50 B
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.49f1, 6000.1.4f1, 6000.2.0a9
Reproducible on: macOS Sonoma 15.3 (M2 Ultra)
Not reproducible on: Windows 10 (22H2), Windows 11 (24H2)
Notes:
- Related Discussions thread: [https://discussions.unity.com/t/hdrp-17-1-0-generates-garbage/1633271]
- Metal Graphics API must be used to reproduce this, making the issue reproducible only on macOS
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment