Search Issue Tracker
Fixed
Fixed in 1.8.6
Votes
3
Found in [Package]
1.8.6
Issue ID
TB-269
Regression
Yes
Runtime performance degrades when an Audio Track contains a lot of Audio Clips
Reproduction steps:
1. Open the attached “BugRepro“ project
2. Open the “Assets/Scenes/SampleScene“
3. Open the Profiler window (Window > Analysis > Profiler)
4. Enter The Play Mode
5. In the Profiler window, start the recording
6. After a couple of seconds, stop the recording
7. In the CPU usage module window, select Hierarchy
8. Find the “PostLateUpdate.UpdateAudio“ process and observe its “Time, ms“ reading
Expected result: “PostLateUpdate.UpdateAudio” takes an insignificant time, unaffected by the Audio Clip amount in the Audio Track
Actual result: “PostLateUpdate.UpdateAudio” takes 500ms or more
Reproducible with: 1.7.6 (2022.3.17f1), 1.8.6 (2022.3.17f1, 2023.2.5f1, 2023.3.0a19)
Not reproducible with: 1.7.6 (2021.3.35f1), 1.8.6 (2021.3.35f1)
Fixed in: 1.7.6 (2022.3.18f1), 1.8.6 (2022.3.18f1, 2023.2.6f1, 2023.3.0b1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (1)
-
Peter77
Feb 09, 2024 16:42
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Fixed by another fix, could not reproduce locally.
Resolution Note (fix version 1.8.6):
Fixed by another fix, could not reproduce locally.
Resolution Note (fix version 1.8.6):
The issue was fixed in 2022.3.18f1, 2023.2.6f1 and 2023.3.0b1 Editor versions