PyNodes Leak Memory Upon Refresh #37460

New Issue

Atomic · 2013-11-14T23:58:44+01:00

Atomic commented

2013-11-14 23:58:44 +01:00

System Information
Operating system and graphics card
Windows 7 x64 8Gb
nVidia gtx460

Blender Version
2.69 official release.

Short description of error
PyNodes Leak Memory Upon Refresh

Exact steps for others to reproduce the error
Open up default Blender and go to the text window.
Run the template code for Custom Nodes
Add a node window to Blender, New Tree and Add a Custom node to the window.
Observe the memory report along the top of the Blender interface.
Now select the Node and press G-Key to drag it around the window.
Click to release the node and observe that memory usage has gone up.
Repeat the process and you will see that memory keeps going up.

Other actions upon the node will leak memory as well. Try scrubbing the integer property value a few times.

I hope that is enough info to test this bug.

**System Information** Operating system and graphics card Windows 7 x64 8Gb nVidia gtx460 **Blender Version** 2.69 official release. **Short description of error** PyNodes Leak Memory Upon Refresh **Exact steps for others to reproduce the error** Open up default Blender and go to the text window. Run the template code for *Custom Nodes* Add a node window to Blender, New Tree and Add a Custom node to the window. Observe the memory report along the top of the Blender interface. Now select the Node and press G-Key to drag it around the window. Click to release the node and observe that memory usage has gone up. Repeat the process and you will see that memory keeps going up. Other actions upon the node will leak memory as well. Try scrubbing the integer property value a few times. I hope that is enough info to test this bug.

Atomic commented

2013-11-14 23:58:44 +01:00

Changed status to: 'Open'

Atomic commented

2013-11-14 23:58:44 +01:00

Added subscriber: @AtomP

Lukas Tönne was assigned by Bastien Montagne

2013-11-15 12:44:21 +01:00

Bastien Montagne commented

2013-11-15 12:44:40 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2013-11-15 12:44:40 +01:00

Lukas, think this is for you :)

Lukas Tönne commented

2013-11-16 18:02:24 +01:00

This is not limited to custom nodes at all. It happens with virtually everything i checked, regular nodes as well as e.g. texture buttons. There are no warnings by guardedmemalloc or valgrind either, so i don't think it's critical.

My guess is that it's simply the undo system: if you set undo steps to 0 the memory increase only happens during the operator execution (like increase when grabbing a node, then drops back after releasing).

This is not limited to custom nodes at all. It happens with virtually everything i checked, regular nodes as well as e.g. texture buttons. There are no warnings by guardedmemalloc or valgrind either, so i don't think it's critical. My guess is that it's simply the undo system: if you set undo steps to 0 the memory increase only happens during the operator execution (like increase when grabbing a node, then drops back after releasing).

Lukas Tönne commented

2013-11-16 18:07:06 +01:00

Changed status from 'Open' to: 'Archived'

Lukas Tönne closed this issue

2013-11-16 18:07:06 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

PyNodes Leak Memory Upon Refresh #37460