[BUG] Indigo - hard to stop when using network rendering?

[Doug Armand]

I think it's been mentioned before but it is still a big annoyance for me that when I am doing a large render if I use a slave on a different computer and decide to Quit Indigo it takes ages for it to completely release memory, resources, etc.

For example I am often rendering large enough that Indigo will use 5-6GB of my paltry 8GB Ram. If I render with no network rendering I can usually quit Indigo and it will normally release the RAM, etc pretty quickly. If however I am using network rendering then it seems to take ages to fully release - in the meantime my computer is pretty much unresponsive, etc.

I have now gotten into the habit of using Task Manager to kill the Indigo process because it is so much quicker than waiting for Indigo to do it itself. For clarification the Indigo GUI will usually quit fairly quickly, though not always, but Indigo is still running, and using ram and resources, according to Task Manager.

Like I said above I think it may somehow be related to using network rendering?

[suvakas]

Yes, it is related to network rendering.
When you quit your working master, then slaves will automatically upload everything they have and only after that your main GUI closes. The higher the resolution the longer it takes for slaves to upload.
So this is not a bug, but a feature. Specially useful when rendering animation over network.
It makes sure, that no sample gets wasted.

[Doug Armand]

Yes, it is related to network rendering.
When you quit your working master, then slaves will automatically upload everything they have and only after that your main GUI closes. The higher the resolution the longer it takes for slaves to upload.
So this is not a bug, but a feature. Specially useful when rendering animation over network.
It makes sure, that no sample gets wasted.

Well I'd prefer an option not to - I don't, yet, render animations so this is a real PITA for me but thanks for at least explaining why it happens

[benn]

Sounds like an annoying bug to me.

Added to the bugtracker to be fixed in 2.4.

[Doug Armand]

Sounds like an annoying bug to me.

Added to the bugtracker to be fixed in 2.4.

Cool - I see it as a bug as well - when I quit a program I don't expect it to still be running a few minutes later

[suvakas]

But please don't f*ck up the animation rendering when fixing this "bug".

Only thing I see could be done here is to detect if the program wants to close because of user actions or because max samples per pixel are reached.

[OnoSendai]

I can make it an option, so either it can shut down immediately (default?) or will collect all frames from slaves (when enabled, for animation).
Sound good?

[suvakas]

Yes, sounds good.

[Doug Armand]

I can make it an option, so either it can shut down immediately (default?) or will collect all frames from slaves (when enabled, for animation).
Sound good?

+1