Google Chrome crashed on me, as it often does. But when I restarted it the chrome (UI elements) is suddenly huge: the tab text and favicons, UI icons, address bar font, etc. Also, when I open new pages, zoom is set to something > 100% even though page zoom is set to 100% in settings. This is currently Chrome 36, in Windows 7 Home Premium x64.
In Windows I've had a custom DPI scaling of 149% and "Use Windows XP style DPI scaling" enabled forever. However I had Chrome setup was working properly with those settings for many months until today. I thought I recalled enabling a Chrome flag related to "high DPI" way back when. When I checked today, all I see is "Force high DPI mode" (force-device-scale-factor) and it's "not available" (grayed out). I found this recent discussion talking about a --high-dpi-support flag being eliminated in favor of a registry entry. I tried adding --high-dpi-support=1 to my shortcut, but it has no effect. Adding a --force-device-scale-factor does have an effect, but that seems like a kludge.
1) If the --high-dpi-support flag has been eliminated in favor of a registry entry, how is that supposed to work with a portable installation?
2) How and why would this problem only have manifested suddenly today after Chrome crashed? I believe the last time I updated Chrome was several weeks ago.
3) How do I fix it?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
This is the bane of so many Chrome users and a bug report has been filed on it. Open GoogleChromePortable.ini in your favorite text editor and add the parameters below to "AdditionalParameters=" (I show it in line 14):
/high-dpi-support=1 /force-device-scale-factor=1
If you haven't added any other parameters modified line should read:
AdditionalParameters=/high-dpi-support=1 /force-device-scale-factor=1Save the file, close Chrome (and make sure it's fully closed and all settings are written to the portable location) and restart Chrome. This fixes the problem on my system and should work for others.
Thanks for your reply. And sorry for the delay in my response.
Hmm, I don't think I'd seen that issue, but they're complaining about v 37, and I'm having the problem in v 36.
As I noted about passing command line flags to the Chrome executable, the
force-device-scale-factorparam does have an effect, but seems like a kludge to me. I don't believe the/high-dpi-support=1param does anything. According to that discussion I linked to, that was eliminated as a flag, in favor of a registry entry. All of the following appear to have the same effect to me:AdditionalParameters=/force-device-scale-factor=1AdditionalParameters=/high-dpi-support=1 /force-device-scale-factor=1AdditionalParameters=/high-dpi-support=0 /force-device-scale-factor=1Do you get different effects from any of those?
Thanks, I didn't know about
GoogleChromePortable.ini. For anyone else who needs to know this: the only one I had was in/Other/Source. I created one in/(the Chrome portable directory). You have to have this part in the file (at the top I'm assuming):[GoogleChromePortable]