Is this an oversight or a deliberate policy? Remote_CoGetClassObject creates the local server process and hands over to create_marshalled_proxy If create_marshalled_proxy can't immediately find the pipe then it will create the process again.
Is it safe to drop the first one? How about the second? It looks to me as if Remote_CoGetClassObject is the only place that calls create_marshalled_proxy so I presume we can remove either. Bill
