Search Issue Tracker
Fixed in 2018.1.X
Won't Fix in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.1.0p4
Issue ID
944500
Regression
No
[OSX] WebRequestUtils.MakeInitialUrl causes CPU spikes
To reproduce:
1. Open project attached by QA on computer with OS X
2. Open "main" scene
3. Open profiler tab, enable record and deep profiling. Focus profiler on CPU
4. Enter play mode and hit Run Test button in game window
5. Inspect the profiler
Expected: WebRequestUtils.MakeInitialUrl should cost less time (now ~70ms), it shouldn't cause spikes.
Reproduced with: 5.5.0f3, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
OS: macOS Sierra 10.12.6 (16G29)
Note: Doesn't reproduce on windows (WebRequestUtils.MakeInitialUrl takes ~10ms)
Fixed in 2018.1.0a5
The issue was addressed by adding a new set of APIs to UnityWebRequest, that take instance on System.Uri instead of string URL.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment