Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X
Votes
0
Found in
2017.1.0f3
Issue ID
931839
Regression
Yes
InputSystem allocates 17 bytes of memory to NativeInputSystem.HasDeviceDiscoveredHandler() in every frame
Reproduction Steps:
1. Import attached project.
2. In Build Settings, make sure "Autoconnect Profiler" is selected.
3. Add "Scene" to build.
4. In Unity Editor menu, select File -> Build and Run.
5. Select "Play".
6. Click around in the Build and observe Profiler.
Expected result: Memory shouldn't be allocated in every frame.
Actual result: Memory is allocated in every frame.
Reproducible with: 2017.1.0f3, 2017.2.0b3
Not reproducible with: 5.6.2p3
Note: If project is built in a previous version, the bug is no longer reproducible in 2017 versions. It is difficult to pinpoint the start of the regression because of this.
Fixed in: 2017.3.0a5, 2018.1.0a1
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
jmitcheson
Oct 02, 2017 12:51
I am seeing this on Unity 2017.2.0f1 too. 9B/frame on Android
dustinkerstein
Sep 28, 2017 17:49
I can still replicate this in Unity 2017.2.0f1