Please excuse any errors; mailing lists are confusing.

While wrapping up work on a system that includes 5 custom icenodes, I
noticed that memory usage was increasing by about 1mb per second during
playback.

I eventually narrowed it down to a per-point-array node, the only
single-threaded node in the setup. In a test scene I have it reading about
30 turbulized mesh point positions and spitting them into a single
per-object array, and after leaving it for 15-30 minutes a while memory
usage had increased from 400mb to 1.5gb. It is not released until the
program is closed.

Being at loss as to what might be causing it I removed everything but the
absolute necessary pieces of the code (port declarations etc), only to find
that the problem persisted.

Next I created a new icenode using the wizard, adding one input and one
output port with the default settings, and setting it to single threaded.
This also slowly increases memory consumption when executed. Using an 8x8x8
grid as input it increases memory usage by about 150kb per second.

If the input is singular (object context) there is no perceivable increase
in memory usage. The rate of increase appears to be relative to the number
of input components.

I primarily use Softimage 2011, but running it in the 2014 trial produces
the same result. Were it a legitimate bug it would seem unlikely that it
would persist for so long.

Could anyone shed some light on what is going on here? Is this normal?

Thanks
--------------------------
To unsubscribe: mail [email protected] with subject 
"unsubscribe" and reply to the confirmation email.

Reply via email to