KX_GameObject pyattr getters leak memory #44919

New Issue

mobious · 2015-06-02T00:31:22+02:00

mobious commented

2015-06-02 00:31:22 +02:00

System Information
Windows 8 64-bit
NVIDIA GeForce GTX 765M

Blender Version
2.74 000dfc0

Files
memoryleak.blend -- Contains an empty with a Python module setup to add and remove 1000 default cubes every frame after the space bar has been pressed. After each cube is added, its localPosition attribute it referenced (not saved).

Description
Getting certain game objects' attributes seems to cause a memory leak.

Exact steps for others to reproduce the error
In the attached file, start the game engine. Note the amount of memory currently used. Press space once to start adding objects. Note how Blender's memory usage continues to increase even though all the objects are removed and no references to the mathutils Vectors returned by referencing localPosition are saved. The increase is about 250KB/sec on my machine.
You can confirm the increase is caused by referencing the localPosition attribute by commenting out line 19 in the script and repeating the process.

Additional Notes

Getting an attribute many times on a single object does not leak memory. The attributes must be on new objects for memory usage to increase.
Setting an attribute does not cause memory to leak, as can be seen in line 23 of the script.

**System Information** Windows 8 64-bit NVIDIA GeForce GTX 765M **Blender Version** 2.74 000dfc0 **Files** [memoryleak.blend](https://archive.blender.org/developer/F183063/memoryleak.blend) -- Contains an empty with a Python module setup to add and remove 1000 default cubes every frame after the space bar has been pressed. After each cube is added, its localPosition attribute it referenced (not saved). **Description** Getting certain game objects' attributes seems to cause a memory leak. **Exact steps for others to reproduce the error** In the attached file, start the game engine. Note the amount of memory currently used. Press space once to start adding objects. Note how Blender's memory usage continues to increase even though all the objects are removed and no references to the mathutils Vectors returned by referencing localPosition are saved. The increase is about 250KB/sec on my machine. You can confirm the increase is caused by referencing the localPosition attribute by commenting out line 19 in the script and repeating the process. **Additional Notes** - Getting an attribute many times on a single object does not leak memory. The attributes must be on new objects for memory usage to increase. - Setting an attribute does not cause memory to leak, as can be seen in line 23 of the script.

mobious commented

2015-06-02 00:31:22 +02:00

Changed status to: 'Open'