Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0b8
2019.1.0a3
Issue ID
1086532
Regression
Yes
Memory leaking when selecting an Audio Source in Editor
Steps to reproduce:
1. Open new project
2. Add Audio Source to scene
3. Select it in hierarchy
4. Observe in Task Manager Unity taking up more and more memory, while GPU usage is also spiked
5. Deselect Audio Source, memory is not cleared
6. Select it again, Memory keeps piling up
Expected: Memory is flushed, cleared or not even used unnecessarily in the first place
Actual: Allocated Memory keeps piling up without being cleared.
Reproduced on:
2018.1.0b8, 2018.1.0b10, 2018.1.0f1, 2018.1.9f2, 2018.2.10f1, 2018.3.0b4
Version 2019.1.0a3 (0e3c7820a690)
Sun, 30 Sep 2018 14:48:41 GMT
Branch: trunk
Not reproduced on:
2017.4.12f1, 2018.1.0b1, 2018.1.0b6, 2018.1.0b7,
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment