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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
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.