Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a3
Issue ID
1156341
Regression
Yes
SystemInfo APIs take enum parameter create GC.Alloc
Steps:
1. Open attached project, open repro scene
2. Hit play
3. Open Profiler > CPU Usage
4. Look at Hierarchy > PlayerLoop > Update.ScriptRunBehaviourUpdate > BehaviourUpdate > NewBehaviourScript.Update()
Actual: There is GC.Alloc under the item
Expected: There is no GC.Alloc
Reproducible in: 2019.3.0a3, 2018.4.1f1, 2018.2.20f1, 2018.1.0a5, 2018.1.0a4, 2018.1.0a3,
Not reproducible in: 2018.1.0a2, 2018.1.0a1, 2017.4.26f1, 2017.1.3p1
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2019.3.X):
GCAlloc is due to Textureformat enum check. To avoid GCAlloc, you just have to cache any systeminfo information. ( don't call it per frame )