RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.
Options
I'm running the latest beta, v4.52.01 (Any Cpu) and one of my larger queries that takes ~90 seconds to run, and occupies ~5 GB of ram now returns "RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified." and none of the hyperlinqs respond to their normal actions. The only thing I changed was upgrading to the beta from the production version. I assume this has to do with the new separate process logic for debugging. Could this just be an IPC timeout?
Let me know what to try,
-Karl
Let me know what to try,
-Karl
Comments
-
I've experienced this exception since the switch to query processes. It seems to occur after I awake my machine from hibernation. Hitting Ctrl + Shift + F5 recycles the appdomain and the exception goes away.
-
Thanks, I will give that a shot.
-
I'm working on replacing Remoting with a custom IPC built atop shared memory, so this problem will go away in subsequent builds.
-
The new shared memory channel is now complete and Remoting has been expunged. There have been some performance improvements with this, too. Let me know how you get along:
http://www.linqpad.net/beta.aspx -
Any chance said shared memory channel can be used by a third party? A nuget package maybe?
-
What's the scenario in which you'd like to use it? The channel is tailored very much around the requirements of LINQPad, and so would need quite a bit of work (and documentation) to be generally useful.
-
Just a general purpose replacement for the IPC channel. I'm using remoting to communicate with a launched VS instance to run integration tests using xunit. Source at https://github.com/kzu/xunit.vsix
-
Ah, then it won't help. It doesn't use Remoting; it's a (sort-of) replacement for Remoting (with a lot of missing features).
-
I see. Thanks anyway!
