Ubuntu Gnome Freezes when I switch chrome to fullscreen

I am experiencing a weird issue with Chrome on Ubuntu Gnome:

I can't put Chrome on fullscreen because it freezes the system. Actually the system just seems to be frozen, but I can't use it because it only show a static blueish screen (as the hue were changed to blue) from Chrome on top of everything.

The problem doesn't occur when using Opera.

I am able to resume normal use after restarting Gnome Shell (inputting r after pressing Ctrl+F2).

I did find some similar issues from other users, but can't find a solution/workaround:

• Fullscreen Chrome video causes Ubuntu to crash: Turning hardware acceleration off has no effect.
• Making youtube fullscreen will freeze Unity (the whole desktop): I ditched canary because other issues, but tested in stable and the problem still persist.

OS Info:

• Ubuntu 17.04 64-bit (dev branch)
• GNOME Shell 3.24.0
• NVIDIA 378.13
• Google Chrome 58.0.3029.54 beta

I am using openSuse Tumbleweed on a Lenovo T460s and experiencing the same problem after updating gnome to 3.24. I was able to pin down the cause to the - Hide Top Bar Gnome Extension After disabling the extension fullscreen works again.

If you are using this or a similar extension, try disabling it for now.

Digging further I found the problem related to animations in gnome-shell ui packages (clutter?). The bug only appeared if the application window (chrome, shotwell) was already maximized before going fullscreen.

The freeze occured when entering fullscreen as well as leaving fullscreen:

1. Full screen any application -> Freeze -> Alt+F2 -> r (Video runs in fullscreen)

2. Exit full screen -> Freeze -> Alt+F2 -> r (Back to desktop)

By disabling animations (tweener) in Hide Top Bar Source panelVisibilityManager.js I was able to make 2. work again. 1. is related to Hide Top Bar removing and adding the PanelBox. I did not find a fast workaround that would also autohide the topbar.

It turns out to be the problem with fractional scaling. Mine was scaled at 125% if it is turned off(back to 100%) the issue resolves.