Thread

Vray eats memory!

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

Vray eats memory! // Bugs

1  |  

Post by Changa // Aug 14, 2007, 4:41am

Changa
Total Posts: 187
pic
Hi,

I found out that every rendering of the same scene with the same camera position decrease available RAM by some fixed for each scene amount. TS does not release this amount of used memory after rendering. For example in my test scene this add on is 130 MB and the figures of used RAM is 0.99GB - 1.12gb - 1.25gb -1.38 gb. The sequence finishes near 2 GB and TS restarting is required to release the memory and return to the initial figures.

Can anyone confirm this abnormal memory leakage in Vray 1.51 rendering?


TS 7.51, Vray 1.51, Win XP Pro, 4 GB Ram, Dual Xeon 3.4

Post by Shike // Aug 14, 2007, 4:53am

Shike
Total Posts: 511
pic
What are the exact situation?

Are you rendering from Model or Workspace,

is Bridge on,

are you using Lightmap in GI (memory hogger),

using HDRI...


My current "Workspace only" project takes between 1-1.2 Gb when rendering...but I havn't noticed the things mentioned. :confused:

Though, I only check that it doesn't reach too high memory consumption...haven't checked if there's a steady increase.

Also, I constantly minimize the tS window which seems to clear the memory..?

(really curious as to what actually happens during minimize...)

Post by Jack Edwards // Aug 14, 2007, 5:05am

Jack Edwards
Total Posts: 4062
pic
It'd be good to isolate exactly where this memory leak is, so any specifics you can give Changa would help out. A simple scene that can duplicate the results would be a huge help.


Tiles I think posted a similar problem as well.


-Jack.

Post by Changa // Aug 14, 2007, 5:09am

Changa
Total Posts: 187
pic
What are the exact situation?



Model side rendering (and most probably also WS, but I vave no time to check it well), Bridge is off, GI and one Inf light, no light map, no HDRI. Background image/colour - does not matter. Monitored with Win task manager.

Post by Changa // Aug 14, 2007, 5:42am

Changa
Total Posts: 187
pic
I've tried now with a simple scene - coffee machine from TS model side library on the cube and with the same (above) settings. Rendering adds 2Mb each time.

Post by Shike // Aug 14, 2007, 8:32am

Shike
Total Posts: 511
pic
Ok, tried it with the coffemachine, Modelside, bridge ON (for Vray to work)

and yes... it seems to become 2Mb larger each render.


Also tried it on WorkSpace (since bridge can be OFF there) and it only adds 1Mb each render....so the bridge might have some influence.


And while in Workspace.... after a couple of renders I was up to

75Mb

Minimized window...and maximized again

34Mb

after first render

63Mb

after that same increments as above.

What exactly is cleared from memory during minimize!?!?

And couldn't that be done automatically after each render?

Post by Shike // Aug 14, 2007, 9:03am

Shike
Total Posts: 511
pic
Tried again with my current Workspace only, bridge off scene.
824000 polys. one texture 1000x1000 on 25 objects, and one 3000x3000 tex.
GI (no lightmap), but only a 640x480 render instead of my usual 5000x3536 ;)

528Mb -> 538Mb after render.
minimize, maximize ( I've added the VirtualMem column on win task mangr now, and it seems like that's where the stuff ends up.)
226Mb -> 238Mb after render ( VMem size increases with same factor.)

Looks like the increment is between 1-2% independant on scene size?

Post by Changa // Aug 14, 2007, 10:44pm

Changa
Total Posts: 187
pic
Checked with Vray 1.52 - the same memory leakage plus fake shades from transparent shaders (I'll keep it for the next bug thread :) )

Post by Shike // Aug 15, 2007, 2:39am

Shike
Total Posts: 511
pic
Ops, I only tried it with Vray1.52 ... at least it's consistent between versions ;)
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn