Memory problems

[Rich_Art]

Hi All,

Does Vrayforc4d release the used memory after closing a project?
When I render a couple of times with vray and I want to render a scene with AR for example I often get a not enough memory error.
When I close C4D and start again I can rendere the scene without any problems.
It looks like Vray does not give back all the memory after closing a project..

Peace,
Rich_Art. :wink:

[marshalartist]

Try removing the rest of your plug-ins temporarily and see if it still does it, it sounds like a memory leak. It might be vray or maybe a rogue plug-in.

[glass.use]

i don't think so, im using vista (suck with a lot of problems) and low performance but vray works pretty good and not using any ram after closing c4d project, although its better to restart c4d if it was a large project

try using any of ram cleaning softwares, it helps :wink:

[Fluffy]

Vista handles memory differently than XP (read : better), so we can't really compare.
I also ran into the same problems, only when using Vray.
I already reported the issue to Renato, but feel free to report as well since the more info he has, the better he can track this.

[glass.use]

i meant that XP works better than vista
and Vray works on my vista like a charm
so it will not be a problem to XP to run it better

not comparing but just want to say that it works fine with me on a stupid OS =P

[RenatoT]

Hello,

i've have some unresolved (for now) memory leak.. but can be, after a day of work.. around 1.. 2Mb.

So i don't think so... but i would like to test what you mean Rich_Art, can you describe me how i can reproduce this problem?

best regards
renato

[Rich_Art]

Hi Renato,

It is very easy to describe. I have 2gig of ram (after the weekend 4gig :) and winxp 64bits)
I just did some testing with vray. Very simple scene's I rendered a couple of times. Close the scene and after that I wanted to render the final scene from the kiteman DVD. The rabbit with the hair. I used AR to render the scene becasue of the hair. When the hair is almost calculated I get an out of memory error.
I close C4D and start it again and it renders without any problem.
I noticed that everytime I do a lot of test renders with vray, c4d comes with the out of memory error.
And even if I not render with AR but only a couple of times with Vray C4D starts to give the out of memory problems. Until I restart C4D.

Peace,
Rich_Art. :wink:

[maya69]

Renato (sorry but english is bad )

When you think solved memory probleme ?

-in few day or few week or few month ?

best regard

[Fluffy]

Renato, the problem is simple : I play with Vray a while, I launch a few renders and such, then I close my current scene.
So, with only the C4D interface opened, memory will still idle at 2Gigs or more (I have the 3GB switch), and not release memory until I close C4D completely and reopen the application (which will then drop at around 500MB with the C4D interface alone).

So I can conclude that somehow Vray is leaking memory and not releasing that 1.5Gigs or more of RAM when the render finishes.

[RenatoT]

Hello all,

i see that is cinema that not release the memory after the rendering.

But if you render again the scene the memory is freed then reallocate to prepare the geometry.

I wrote to maxon to solve this problem.... but you are meaning that after each rendering the memory use grow?

cheers
Renato

[simonw]

surely it has always been the default in cinema to hold the scene in memory after rendering as long as possible?

you can see this in the fact that when first rendering a scene there is a pause while the geometry and textures are loaded at the beginning (the status bar reads 'preparing...') but if you then re-render the same scene there is no pause (everything is still available). however if you load a new scene and render that then the render cache is flushed and the geometry and textures are loaded again.

the bug would be if the memory is not released when the cache need to be flushed because you are rendering a new scene (or a changed scene).

cheers, simon w.

[Fluffy]

Yes, so I guess it's not completly flushed when it should. Some memory stays loaded no matter what, and subsequent renders will give an out of memory error after a while.

[Tong]

Hello all,

i see that is cinema that not release the memory after the rendering.

But if you render again the scene the memory is freed then reallocate to prepare the geometry.

I wrote to maxon to solve this problem.... but you are meaning that after each rendering the memory use grow?

cheers
Renato
so they did`nt fixed it, it`s problem from 8 version and it`s so on :evil:

[Rich_Art]

I'm gald that I'm not the only one with this problem.
I know there is a script for C4D that flushes the mem.
Only I don't know where I've seen that. Could it be the 3DFluff site?

Peace,
Rich_Art. :wink:

Edit: http://forum.3dfluff.com/showthread.php?t=56 altough I don't think this script will solve the problem.

[akiefer]

I work on a MacPro system with 8Gb RAM and have also experience out of memory errors lately.

It happens after extensivley rendering with VRay and then suddenly even a very simple scene will say out of memory when I want to render.

Restart solves it but that is not a nice workflow :)

There also a slow down that I can totally contribute to Cinema 10.5 in using the color slider bars (nothing related to VRay...) There is a hesitation when I start to drag which is very annoying. This is now on the of the hesitation that I have been getting since 10.x when first using any drop down menu in the shader channels or effects tabs (trying to open that triangle for the drop down menu... it takes some 3 to 4 seconds the first time)

Albert

[scanmead]

Noticed the lag on drop-downs here, too, as far back as R9.6. I've always suspected the browser use within Cinema is causing this. Even after closing Cinema, I have to wait to shut down the system for several minutes, while Cinema finishes whatever it's doing.

[glass.use]

Noticed the lag on drop-downs here, too, as far back as R9.6. I've always suspected the browser use within Cinema is causing this. Even after closing Cinema, I have to wait to shut down the system for several minutes, while Cinema finishes whatever it's doing.

i have 2 problems then, i just thought it normal..

drop-down menus lag for 3-4 seconds sometimes
sometimes if i apply displacment on some object
and keep tweaking it like putting the amount from 1 cm to 2 then 3 then make it back to 1 also the shif

it will make the render unbelieveable, it make it laaaaaaaging and slowwwwwwwwwwwwwwwwww abd have no end only stuck at exporting objects


hope this help :)

[akiefer]

maybe this is something we should take to Maxon... Is there a forum like this there too?

Albert

[Laurent]

One thing I have noticed is when I render the same scene the memory usage goes up and up, I though of a memory leakage, the funny thing is when the " not enough memory" warning pops up, I go ahead and rendered every time anyway without problem!

[Tong]

maybe this is something we should take to Maxon... Is there a forum like this there too?

Albert

no we should not, they know that from 8 version, it`s not a hot news for they. :twisted:

[simonw]

no we should not, they know that from 8 version, it`s not a hot news for they. :twisted:

what renato posted is not a bug as i mentioned before.

you guys need to create a small test scene for maxon to show the problem that you are encountering but as far as i can see there is no trouble with the way cinema is handling memory.

i spent the whole week last week with a scene open that took up 1.3GB of memory on my 2GB PC rendering multiple elements for a large matte painting (while working in photoshop at the same time) and never had a single hiccup.

if maxon did know about a dangerous memory leak when R8 was released then it certainly wouldn't be around now. maxon are very scrupulous to squash any memory leaks or crashing bugs in the next release after discovery.

cheers, simon w.

[simonw]

oh, and i should mention that if anyone has a bug that is reproducible and can be shown in a simple scene then maxon has a web page where you can report this problem and it will be entered into the bug database maxon hold.

cheers, simon w.