Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2017.4.0f1
2017.4.15f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1101314
Regression
No
[WebGL]CPU usage by AudioSource.Update increases when audio clips are played in Chrome
To reproduce:
1. Open attached project ("ChromeAudioSource")
2. Open "Main" scene
3. Switch to WebGL platform
4. Build and Run the development build of the project with Autoconnect Profiler option enabled
5. Press the Play1 button and check the CPU load with Profiler
(repeat last step for more visible usage increasement)
Expected: AudioSource.Update usage stays the same over time
Actual: AudioSource.Update continuously increases over time
Reproduced with: 2017.4.19f1, 2018.3.3f1, 2019.1.0b1, 2019.2.0a3
Notes:
- Increased CPU usage by AudioSource.Update is more visible after ~20min of playing the clip
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment