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

Issue 745787 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

application chrome.exe has been blocked from accessing graphics hardware

Reported by syh...@gmail.com, Jul 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. 
2. 
3. 

What is the expected behavior?
Chrome crashes & shuts down then restart

What went wrong?
Chrome crashes & shuts down then restart

Crashed report ID: NO

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 26.0.0.137
 
Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Thanks for filing the issue, can you please elaborate in detail what exactly the issue is. If possible can yo please do a system restart, relaunch chrome again. Also if you can navigate to chrome://crashes, please help us with a crash ID.

Thanks.!
Labels: Needs-Milestone

Comment 3 by syh...@gmail.com, Jul 26 2017

crah :

"Application chrome.exe has been blocked from accessing Graphics hardware."

My drivers are up to date
Nvidia GT710
windows 10 pro 32bit

Project Member

Comment 4 by sheriffbot@chromium.org, Jul 26 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ranjitkan@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

Comment 5 by ajha@chromium.org, Jul 27 2017

Components: Internals>GPU
Labels: Needs-Feedback
Adding proper component for respective team to look at this and requesting to attach chrome://gpu of the system where the issue is seen.

Comment 6 by syh...@gmail.com, Jul 27 2017

please see attached screen capture jpg file of the issue ..  chrome crashes over 10 times within 5-6 hours ...  no issues with microsoft edge ...
Thanks
Screenshot (1).png
20.2 KB View Download
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 27 2017

Cc: ajha@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ajha@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

Comment 8 by enne@chromium.org, Jul 28 2017

Labels: Needs-Feedback
Does Chrome start at all? If so, can you print out what chrome://crashes says?

If Chrome doesn't start, can you try launching Chrome with the --disable-gpu command line flag and then seeing what chrome://crashes says?  See: https://www.chromium.org/for-testers/command-line-flags for information on running Chrome with a command line flag.

Comment 9 by syh...@gmail.com, Jul 28 2017

HI

I cant start  launching Chrome with the --disable-gpu because that is the
only source of display i have , this is getting quite frustrating as the
issue is been going on for a couple of weeks now & i all get in reply from
you guys is supply further info about this or that ...  if you browse the
issue online you will find out that i am not the only 1 who is having these
issues ...  there are so many people out there who are having these issues
specially with there new GPUs or specially with Nvidia cards ..
I am disappointed in the reply/service i am getting from you guys ...
Project Member

Comment 10 by sheriffbot@chromium.org, Jul 28 2017

Cc: enne@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "enne@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

Comment 11 by enne@chromium.org, Jul 28 2017

Labels: Needs-Feedback
I'm sorry, your response isn't very clear to me, so it's hard to know where to take this bug from here.

Did you try running with the --disable-gpu flag? If so, did you get a different error? The same error? Were you able to get to the chrome://crashes page while using that flag? Just saying "I can't" is not very helpful for me in understanding what's going wrong on your machine, sorry.

Comment 12 by syh...@gmail.com, Jul 28 2017

sorry no idea what you are talking about ...  neither i know how to do it
.."--disable-gpu flag" ..!

Comment 13 by enne@chromium.org, Jul 28 2017

Please look at https://www.chromium.org/for-testers/command-line-flags, that should explain how to pass an additional command line flag to chrome.
Project Member

Comment 14 by sheriffbot@chromium.org, Jul 28 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "enne@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

Comment 15 by enne@chromium.org, Jul 31 2017

Labels: Needs-Feedback
Status: WontFix (was: Unconfirmed)
As there is no response from the reporter for comment #13 for more than one month.
Hence, closing the issue as wontFix.
Please feel free to raise a new issue if the issue is reproduced with latest chrome builds.

Thanks...!!

Sign in to add a comment