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

Issue 594188 link

Starred by 4 users
Status: Fixed
Owner:
█ kulshin@chromium.org
Last visit > 30 days ago
Closed: Mar 2016
Cc:
█ kulshin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

When I open the browser using "--disable-directwrite-for-ui" line it always displays a "Aw, Snap" message

Reported by wiche...@gmail.com, Mar 11 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1. Use --disable-directwrite-for-ui to open the browser
2. Browser opens and displays "Aw, snap" messages in every tab, even settings one.

What is the expected behavior?

What went wrong?
Chrome doesn't display any website.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: 49.0.2623.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by matthieu...@gmail.com, Mar 14 2016 

I also have the issue above.

But the "Chrome Canary" works fine with that parameter.

Chrome version: 49.0.2623.87 m (64-bit)
Canary version: 51.0.2677.0 canary (64-bit)
OS version: WIN7

Comment 2 by yusukes@chromium.org, Mar 16 2016

Cc: kulshin@chromium.org
Components: UI>Browser>Core
Status: Untriaged (was: Unconfirmed)

Comment 3 by kulshin@chromium.org, Mar 16 2016

Owner: kulshin@chromium.org
Hmm, that makes sense - that switch will cause the browser to not create the direct write factory, but the renderer will still try to use directwrite, so it won't be able to load fonts. You can add the --disable-direct-write switch to have the renderer use GDI as a workaround.

Comment 4 by yusukes@chromium.org, Mar 16 2016

Status: Assigned (was: Untriaged)
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 30 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6c6acc660dcac0ff5f407344e2368f090bd07430

commit 6c6acc660dcac0ff5f407344e2368f090bd07430
Author: kulshin <kulshin@chromium.org>
Date: Wed Mar 30 18:41:31 2016

Move check for --disable-directwrite-for-ui switch

This change will allow the DirectWriteFontProxyMessageFilter to bypass this
switch. This is needed so that the message filter can still load fonts for
renderers which might still be using DirectWrite for font rendering.

BUG= 594188 

Review URL: https://codereview.chromium.org/1839213002

Cr-Commit-Position: refs/heads/master@{#384035}

[modify] https://crrev.com/6c6acc660dcac0ff5f407344e2368f090bd07430/ui/gfx/win/direct_write.cc
Project Member

Comment 6 by bugdroid1@chromium.org, Mar 30 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6c6acc660dcac0ff5f407344e2368f090bd07430

commit 6c6acc660dcac0ff5f407344e2368f090bd07430
Author: kulshin <kulshin@chromium.org>
Date: Wed Mar 30 18:41:31 2016

Move check for --disable-directwrite-for-ui switch

This change will allow the DirectWriteFontProxyMessageFilter to bypass this
switch. This is needed so that the message filter can still load fonts for
renderers which might still be using DirectWrite for font rendering.

BUG= 594188 

Review URL: https://codereview.chromium.org/1839213002

Cr-Commit-Position: refs/heads/master@{#384035}

[modify] https://crrev.com/6c6acc660dcac0ff5f407344e2368f090bd07430/ui/gfx/win/direct_write.cc

Comment 7 by kulshin@chromium.org, Mar 30 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment