Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3.2f1
2019.3.5f1
2020.1.0a22
2020.2
Issue ID
1229502
Regression
Yes
[MacOS] Editor is leaking memory when Aura Camera component is attached to a GameObject in the scene and Aura preview is enabled
Reproduction steps:
1. Open the attached project ("1229502.zip")
2. Open "SampleScene"
3. Press "Enable Aura Preview" in Scene View
Expected result: Memory is not leaked
Actual result: Memory is leaking
Reproducible with: 2019.3.2f1, 2019.3.10f1, 2020.1.0a22, 2020.1.0b5, 2020.2.0a7
Not reproducible with: 2018.4.21f1, 2019.3.1f1, 2020.1.0a21
Notes:
- The issue is not reproducible in Windows
- The issue seems reproducible with 10.14.6, 10.15.3, didn't test other MacOS versions
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in 2019.3.15f1