Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.4.1f1
Issue ID
1019565
Regression
No
[OSX] Memory leak when the scene is played multiple times
[OSX] Memory leak when the scene is played multiple times
To reproduce:
1. Create a new project
2. Open activity monitor
3. Play/stop scene multiple times using CMD+P
Expected: memory usage should be the same each time scene is played
Actual: memory usage increases each time scene is played(2-7MB)
More info in edit
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note (2018.1.X):
This seems to have been fixed in 2018.1