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

Issue 799969 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-02-02
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

display driver crash if Intel GMA 4500MHD is used

Reported by immo.wet...@adtran.com, Jan 8 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. just start chromium

What is the expected behavior?
start without problems

What went wrong?
display driver crashed a few times during opening/restore of tabs.
same machine with ATI Mobile active works fine.
same machine worked fine with a older version from a couple of weeks ago... (May be October ...)

Did this work before? Yes dont know

Chrome version: 65.0.3316.0  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

its a lenovo W500 with ATI fire GL 5700 and Intel Mobile 4500MHD
 
chromium 51.0.2683.0 works fine as expected
Labels: Needs-Triage-M65
Cc: vamshi.k...@techmahindra.com
Labels: TE-NeedsTriageFromMTV Triaged-ET TE-HardwareDependency
Unable to reproduce the issue on reported chrome version 65.0.3316.0 using windows 7 desktop and by using microsoft surface pro Windows 10. As the issue seems triaged using lenovo thinkpad with ATI fire GL 5700 and Intel Mobile 4500MHD adding labels TE-NeedsTriageFromMTV and TE-Hardwaredependency.

Thanks!
Components: Internals>GPU

Comment 5 by piman@chromium.org, Jan 19 2018

Components: -Internals>GPU Internals>GPU>VendorSpecific
Labels: Needs-Feedback
NextAction: 2018-02-02
Can you attach crash ids from about:crashes?
Labels: GPU-Intel
BTW, the 4500MHD is over 9 years old at this point. It will be hard for us to support such old hardware.
The NextAction date has arrived: 2018-02-02
I think I chcked this twice but due to the fact that not chrominium is crashing first but the display driver somehow---- about:crashes is empty
Project Member

Comment 9 by sheriffbot@chromium.org, Feb 2 2018

Cc: piman@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "piman@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
Labels: Needs-Feedback
Anything useful in /usr/log/Xorg.0.log or dmesg after such a crash?

Sign in to add a comment