Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
2
Found in
2017.1.0b3
Issue ID
911661
Regression
No
mono_custom_attrs_from_class leaks memory when empty scene is played multiple times (Old Mono)
To reproduce:
1. Create a new project - set to Old mono runtime
2. Open activity monitor
3. Play/stop scene multiple times
Expected: memory usage should be the same each time scene is played
Actual: memory usage increases each time scene is played
Note:
With unsaved scene:
on 5.3, 5.4, 5.5 increases ~10MB
on 5.6, 2017.1.0 ~20MB
When scene is saved:
on 5.4, 5.5 increases ~1-10MB
on 5.6, 2017.1.0 ~5-12MB
Reproduced on: 5.4.5p2, 5.5.0f1, 5.5.3p3, 5.6.0b4, 5.6.1f1, 2017.1.0b1, 2017.1.0b5
Tested on OSX 10.12.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- 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
Add comment