New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 784134 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

ERROR:browser_gpu_channel_host_factory.cc(108)] Failed to launch GPU process.

Reported by ryan.k.m...@gmail.com, Nov 12 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36

Steps to reproduce the problem:
1. Open a Terminal and enter the following command:
2. /opt/google/chrome/google-chrome --profile-directory=Default http://www.google.com/
3. 

What is the expected behavior?
launch GPU process
Perform action with No Error Message

What went wrong?
[24070:24106:1111/201341.813142:ERROR:browser_gpu_channel_host_factory.cc(108)] Failed to launch GPU process.

Did this work before? N/A 

Chrome version: 62.0.3202.89  Channel: stable
OS Version: Mint 18.2 sonya Kernel: x86_64 Linux 4.10.0-38-generic
Flash Version: 

Thank You for working on this =) Your deeds are noble.
 
Screenshot from 2017-11-11 20.14.56.png
94.7 KB View Download
Cc: divya.pa...@techmahindra.com
Unable to reproduce the issue on reported version 62.0.3202.89 on Ubuntu 14.04
Attaching screen-cast of the same

784134.ogv
1.5 MB View Download
Labels: Needs-Triage-M62 Needs-Feedback
This is from Ubuntu 16.04 base not Ubuntu 14.04
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 14 2017

Cc: manoranj...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "manoranjanr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: thomasanderson@chromium.org
Components: Internals>GPU
Cc: piman@chromium.org

Comment 7 by piman@chromium.org, Nov 15 2017

It's a minor thing that shows up when it opens a new tab in an existing browser. I believe what happens is that we try to preemptively launch a GPU process but terminate the browser process (since we opened the tab in another chrome instance) before we're done connecting to the GPU process.

Comment 8 by fsamuel@google.com, Nov 17 2017

Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
Update: here is another example of what I feel to be related:
http://dpaste.com/2B754JW

Screenshot from 2017-11-25 00.28.32.png
94.8 KB View Download
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 26

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)
Cc: kylec...@chromium.org
Components: Internals>Services>Viz

Sign in to add a comment