Skip to content
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

Failed to start GPU process #25

Closed
dhill2522 opened this issue Mar 22, 2018 · 3 comments
Closed

Failed to start GPU process #25

dhill2522 opened this issue Mar 22, 2018 · 3 comments

Comments

@dhill2522
Copy link
Collaborator

This nasty-looking error has come up when running m.GUI() to launch the gui on some machines.

image

As far as I can tell this is not actually an issue with the Gekko project itself, but is actually an error being thrown from chromium in this case. It is also a problem for our friends on the jupyter project as is evidenced in their issue 2836

@dhill2522
Copy link
Collaborator Author

@loganbeal would you mind trying some of the suggestions from our friends in the above jupyter issue and seeing if that resolves your problem? I have not been able to reproduce it here.

@loganbeal
Copy link
Collaborator

export BROWSER="chromium-browser" before launching spyder does resolve this issue. Is this a reasonable long-term solution? Should we just add a note in the docs to set the appropriate BROWSER environment variable if you're experiencing this issue?

Interestingly, export BROWSER="google-chrome" launches chrome instead of chromium, but chrome can't connect to the server (localhost refused to connect) and the kernel restarts automatically.
Also interestingly, I get the same gpu error when launching chromium or chrome from the CLI:

> chromium-browser 
> Created new window in existing browser session.
[11751:11785:0322/144201.450026:ERROR:browser_gpu_channel_host_factory.cc(121)] Failed to launch GPU process.

@dhill2522
Copy link
Collaborator Author

Maybe we do want to just put a note in the docs until the problem seems to go away or we learn more about it. Either way I do not think it is an issue with our code, so I am closing this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants