Job finishes, but mxnetwork.exe still using cpu cycles

Job finishes, but mxnetwork.exe still using cpu cycles#354014

By Delineator - Tue Mar 20, 2012 4:41 pm

- Tue Mar 20, 2012 4:41 pm #354014

I'm running the manager/monitor on my computer, which is connected to 5 standalone boxes I'm using as nodes. The issue is, after I complete a coop rendering, the process "mxnetwork.exe" is still using a 25% of my cpu power (a single core).

Is this normal? Obviously if I quit/restart the manager I can clear the problem, but I was hoping this was a squashable bug.

Thanks.

Re: Job finishes, but mxnetwork.exe still using cpu cycles#354019

By Bubbaloo - Tue Mar 20, 2012 5:03 pm

- Tue Mar 20, 2012 5:03 pm #354019

Maybe it is still merging the MXI files? Does it ever stop using the 25% or go on indefinitely?

Brian Looney
Maxwell + RealFlow
http://www.turbosquid.com/Search/Artists/Bubbaloo
Help! I'm dispersing into a haze of probability!

Re: Job finishes, but mxnetwork.exe still using cpu cycles#354023

By Delineator - Tue Mar 20, 2012 6:08 pm

- Tue Mar 20, 2012 6:08 pm #354023

Nope, the merging is long since done, but it just keeps using the resource. Its not doing anything, but the process is still occupying one of my cores.

If I kill manager and then restart, it will go away (until I send another job).