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.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
jiangzhen
Mar 20, 2018 16:31
yes!yes!yes!yes!yes!yes!yes!yes!yes!