Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.1p3
Issue ID
966316
Regression
No
Job system doesn't seem to use all cores on Samsung Galaxy Note 4
Steps to reproduce:
1. Open project "anim_vert_example.zip"
2. Build for device
3. Open up Unity Profiler and select TimeLine view.
4. Deselect 'record'.
5. In the timeline, zoom in with the scroll bar on the 250 'AnimatorControllerPlayable.PrepareFrame' tasks until you can see which cores they are executing on.
6. Notice that the jobs are not executing on all 4 cores. Sometimes only 2, sometimes only 1, and the rest of the worker threads can idle.
To see expected results:
7. Press Play to run the project in the editor.
8.Select 'Profile Editor'.
9. In the timeline, zoom in with the scroll bar on the 250 'AnimatorControllerPlayable.PrepareFrame' tasks until you can see which cores they are executing on.
10. Notice that on PC the jobs are executing on all the cores.
Reproduced on: 5.6.5p4, 2017.1.3f1, 2017.2.1p2, 2017.3.0p3, 2018.1.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- IndexOutOfRangeException is thrown in NativePassCompiler when a graphics buffer is used in more than 5 render passes
- "Undo Stack Overflow" error is thrown, and Undo History is deleted when multiselected GameObjects are reparented to their GrandParents
- SearchColumn of type "ObjectReference" does not get refreshed for the custom SearchProvider when lighting generation finishes
- LogWarning is not executed in the HDRP package script when running the project in -batchmode
- Freeze on DynamicHeapAllocator::InitializeMemoryRegion when entering Play mode in a specific scene
Add comment