*close vvvv and restart 40beta16
*open taks manager to observe memory usage of vvvv.exe
*only add one IObox (Value Advanced)
*change the value of the iobox by dragging the right mouse button
*the memory usage of vvvv.exe increases
*but does not fall back.
oh well i think west is right.
every action is put into the history and when dragging at an iobox there might be added some entries per second.
each history entry is a object structure representing an xml snippet.
something like that. each tag or attribute is internally represented by an object to be able to be faster in case of undo/redo.
in the taksmanager it looks like 3KB or so for a single value change (when editing by keyboard). that could be the size of such a object structure. so i think that would be the explanation already.