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

Issue 628925 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
not on Chrome anymore
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Multi-screen Win10 BSOD

Reported by marshman...@gmail.com, Jul 17 2016

Issue description

Crash

Windows 10 Insider Preview 14390 

AMD Radeon GPU with 3 Screens not in Eyefinity mode

Maximising Chrome on left or right screen (not the center primary display) causes chrome to display maximised on the primary screen and the expected side screen then blue screen of death with video scheduler internal error. 

In windowed mode or maximised on primary display no crash.

 
Are you sure this is even a bug with Chromium? You are running the preview of Windows 10, what do you expect. I myself tried multiple monitors with Chromium and it works just fine. Hint hint, this form is for Chromium users not Chrome users.
UPDATE: toggling hardware acceleration fixed it. I would guess something was changed and variables were not converted between versions.
Status: Untriaged (was: Unconfirmed)
Team, could you please look into this issue.

Thank you.
Correction on the Update: turning off hardware acceleration stops the bug but turning it back on brings it back (I hadn't relaunched after turning it back on last time)
sorrlor: direct link from Chrome Canary banner begging for bug reports.  Bug 100 % repeatable. Chrome Canary is the only app to have caused this. The Windows 10 previews are a lot more stable than Chromium. This is the first blue screen of death in over 5 months. 
Components: -UI>Settings Internals>Graphics
Labels: -Proj-MaterialDesign-WebUI

Comment 7 by enne@chromium.org, Jan 25 2017

Components: -Internals>Graphics Internals>GPU
Owner: jbau...@chromium.org
Status: Assigned (was: Untriaged)
Components: -Internals>GPU Internals>GPU>VendorSpecific
Labels: OS-Windows
Status: WontFix (was: Assigned)
Seems like a driver bug, so not much we can do about that.

Sign in to add a comment