Search Issue Tracker
Duplicate
Duplicate in 2017.4.X
Votes
0
Found in
2017.3.0b3
2018.1.0b12
Issue ID
1021880
Regression
Yes
Memory use increasing with repeated Scene loading/unloading
Steps to reproduce:
1. Open attached Unity project (OC link)
2. Build for Windows
3. Run the build for a few minutes (1-2 is enough)
4. Watch it accumulate memory
Expected result: memory is properly unallocated
Actual result: memory is leaking
Reproduced with: 2017.3.0b2 (?), 2017.3.0b3, 2017.3.1f1, 2017.4.2f2, 2018.1.0b12, 2018.2.0a4
Not reproduced with: 2017.1.1f1, 2017.2.1f1, 2017.3.0a7, 2017.3.0b1, 2018.2.0a5, 2018.2.0b3
Note: the build for 2017.3.0b2 crashes so it is possible that the regression occurred there. Marked the regression point as 2017.3.0b3 since I could properly test it.
Note 2: the problem went away in 2018.2.0a5
Note 3: attached a couple of random builds for quicker illustration of the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment