Indigo Renderer Forum

Blender 2.68.0 r58537 64bit & Blender 2.69.0 r60995 64bit
Blendigo 3.6.10.0 & 3.6.17.0
Indigo 3.6.18 64bit

Hello,

I just finished working on a scene that is quite big in terms of number of vertices and texture files (Using particules to generate thousands of objetcs). When I launch an "Animation rendering", the memory on my PC goes ballistic. Rendering a single frame on that scene will have Blender go up to about 2 GB. With 9GB RAM on my PC, I can only reach 22 frames generated for rendering by Blendigo (I reach 9GB used after around 6 frames generated, after that, it's swapping). Once I get to around 22 frames, Windows goes nuts and tells me it had to stop Blender because of low memory.

Just bought more memory and raised my system's memory to 18GB. Guess what!, I get to 18GB memory used after around 12 frames...

If I close Blender, memory is obviously recycled by Windows.

Just to see if the problem could be related to my scene, I tried another scene (much less complexe) and I noticed that memory goes up too but obviously slower since the scene is very simple. (Going up by 200M after 60 frames).

P.S. Once the scenes are generated, Indigo can process them without any problems.

I've noticed Blender eating up loads of memory after exporting as well, though not sure if this is a Blendigo problem or more generally a Blender problem...

Any way of making sure everything is destroyed after export?

Noticed it too. After about 10 renderings, I save the Blender scene, quit, and load it up again to clear the RAM.

I was also thinking it could have been Blender but if I generate an animation for the same scene, I can render (using standard blender renderer) one hundred frames with memory staying at about 700MB steady.

I'm seeing the same behaviour here. I'll try to figure out what's happening.

Found what's causing this and resolved it for the next blendigo release.

Sweet! When? Will it have the new 3.8 freatures in it?

Very nice! Looking forward to next blendigo version!

Just adding that I'm seeing it too - major bad leakage....