I believe the memory leak issue in single threaded node has been worked on.
Should check the next beta release.
Chris
On 2 Oct, 2013, at 5:12 AM, Mathias N wrote:
> If you happen to be running x64, would you (or anyone else listening in)
> mind running the node and scene file below and seei
If you happen to be running x64, would you (or anyone else listening in)
mind running the node and scene file below and seeing if it affects your
memory usage?
http://www.mayulive.com/memleak.scn
http://www.mayulive.com/MemLeakSingleThread.dll
(Post with files attached got stuck in the moderator
This is strange because I'm actually working on a single threaded ICENode and
don't have any memory leaks. The output port is a single structure of type
Vec3 in 0D context.
I can run it on a mesh with 3 millions points for 10 000 frames without
memory issue.
I'm using 2013 QFE7 btw.
On Tue, Oc
Thanks for the reply.
The trial version I'm using is 2014 SP2.
Testing is being done in an empty scene with nothing but the newly created
pointcloud and a simple ice tree. There are no attribute display properties
present.
To rule out any other possible culprits I created two identical nodes that
Hi,
Indeed, there has been some memory leaks issues in the past. If you were
testing in 2014, you should try 2014 SP2 as it fixed (some parts) of the
ICE related memory issue.
If 2014 SP2 doesn't fix the pb you can also check if you've got some
attribute display properties on your objects. They co
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
6 matches
Mail list logo
