Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-398
Regression
Yes
ECS memory leak when refreshing project while in Play mode
Reproduction steps:
1. Open the attached project “MemLeakProject”
2. Open the “Assets/OutdoorsScene” Scene
3. Open the Preferences window (Unity > Settings on macOS) and open the Jobs tab
4. Make sure that the “Leak Detection Level” field is set to “Enabled With Stack Trace”
5. Enter the Play mode
6. Open the “Assets/Scripts/GameSystem.cs” script file in any IDE
7. Add a space on any line at the end and save the script
8. Go back to Unity Editor and refresh the project (Cmd + R or Ctrl + R)
9. Inspect the Console window
Expected result: The Console window is empty
Actual result: The Console contains messages saying that a memory leak happened
Reproducible with: 1.0.8 (2022.2.21f1, 2023.1.0b18, 2023.2.0a16), 1.0.10 (2022.3.0f1, 2023.1.0b19, 2023.2.0a17)
Not reproducible with: 1.0.0-pre.65 (2022.2.21f1)
Reproducible on: macOS 13.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment