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
- New Hierarchy filtering query block remains visible but filtering is not applied when returning from Prefab Mode in Context
- Empty scrollable space appears and scrollbar shrinks when scrolling down in the Tile Palette Brush Picks overlay window and List View selected with many saved brushes
- Player GameObject can’t be selected in the Hierarchy window during Step 4 of the "Get Started" tutorial in 2D Platformer Microgame because Hierarchy window is masked
- Gradient marker colors are removed when undoing marker movement in the Inspector Gradient field
- Crash on RendererScene::NotifyInvisible when GameObjects are deleted from the Hierarchy in a specific Scene
Add comment