Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
972263
Regression
No
IDbCommand ExecuteNonQuery method rapidly allocates memory
Reproduction steps:
1. Download project "MemLeak.zip" and open in Unity
2. Open scene "memtestscene"
3. Open Task Manager
4. Enter Play mode
5. Observe Task Manager
Expected: Unity uses appropriate amount of memory
Actual: Unity begins rapidly allocating memory (actual.gif)
Reproduced on: 5.6.4p4; 2017.1.2p4; 2017.2.1f1; 2017.3.0f2; 2018.1.0a7
Note: commenting out this "cmd.ExecuteNonQuery();" in Script.cs stops the rapid memory allocation
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
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
Resolution Note (2018.3.X):
The process memory size grows much more than the managed heap. This indicates if there is a leak it seems related to native memory usage in the Mono.Data.Sqlite.dll or in the native sqlite.dll itself. However, at this time we are not going to further investigate the issue when using the Mono.Data.Sqlite.dll library.