-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application error at PothosGui startup #151
Comments
Any chance the wifi connection is down? I remember that caused some socket and or dns connection to fail, even though it was just localhost. It just couldnt resolve anything with the windows network config as it was. Just a hunch though: https://groups.google.com/forum/#!topic/pothos-users/HJhjCopYQ6I |
I tried to start PothosGui with only Wi-Fi connection, only Ethernet connection and with disabling all network adapters - no result. All connection settings are by default. |
This is probably a bug in poco (one of the dependency libraries) where its dying in an assert rather than throwing. So rather than a graceful error message, or even recovery, I get this process abort out of no where -- so I know thats not very helpful. And if we do track this down, poco probably needs an upstream patch. Anyway: my second guess is that ipv6 is somehow disabled, and thats also causing it to fail what I assume is some kind of dns lookup for localhost or When I get the chance I will see if any of my other PCs are capable of reproducing this with the latest installer... |
Problem fixed by starting application with administrator privileges. Maybe there is some kind of permissions mismatch. Update: |
This error comes out of poco when the process fails to launch, and we try to read the error stream. Replaced it with something more obvious: bd15485 Specifically for this bug, the windows permissions must have blocked the process from being launched if that make sense. |
Application can't start up and displays the following message:
Windows 10 Pro 1703
The text was updated successfully, but these errors were encountered: