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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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