We open the RV viewer from the monitor fairly often, via a right click script for jobs.
This came up with d6&d7 already, and it appears d8 doesnt fix it neither, but if you open RV from the monitor like this, then close the monitor, you can’t reopen it till you close the RV process as well.
How are you guys launching RV? Is it through Popen, .NET functions, or something else?
We are using Popen, after prepping the env and command line args:
subprocess.Popen(arrCmdArgs, env=envDict)
(The RV launcher library is called from various applications, so we can’t use deadline internal functions.)
Gotcha, makes sense. Does the deadlinemonitor.exe process stick around still? Or is it completely gone? We try to bind to the Monitor’s listening port to determine if another Monitor is already running, so it sounds like the subprocess is somehow preventing the socket from getting cleaned up properly…
Does running the second Monitor with the ‘–new’ flag work, when RV is still open?
It seems gone completely. Using the --new flag opens a monitor.
With RV running, this is what i see in process explorer:
After the monitor is shut down:
But they dont seem to be associated anymore:
Before the monitor was shut down, it looks like this:
Awesome, thanks for the extra info, should help a bunch in finally figuring this one out 
