Snapping a chromium based browser on Windows 10 freezes screen

M

mbeedub

Bit poster
  • Multiple monitors - 3
  • Windows 10 pro
  • Parallels 16.5.1 (49187)
  • Running Parallels in full screen mode

When I snap a chromium based browser to the top of a monitor, the browser window maximizes on that monitor as expected but the monitor freezes.

The browser window also appears maximised on the primary monitor (the one with the taskbar). The only way to resolve this is to switch out of full screen mode in parallels then go back into full screen mode.

The problem doesn't occur when snapping to the top of the primary monitor. It doesn't happen when snapping other windows/applications. And it doesn't happen if snapping to the side of the screen, only when snapping to the top.

It only happens with chromium based browsers. So it occurs with Edge, Brave, Chrome. But doesn't happen with Firefox, Internet Explorer. It's reproducible after a full restart of Mac and Parallels. Have tried various changes to graphics settings etc.

This pretty much makes Parallels unusable on a practical day to day basis.

It seems quite strange behaviour so any thoughts welcome.

Many thanks
 
I'm also experiencing this issue. You haven't included any information about your hardware which would make it difficult for support to help.
I experience this issue when using an eGPU to drive two external 4K60 monitors from a 2020 Mac mini. Are you also using an eGPU by chance?
Like you say, the screens work without issue until you snap a Chromium window to your secondary display. Then that display becomes unusable. There is never a problem on the monitor where the start menu is set (the main display). I have alternated between left and right monitor. Whichever desktop has been set as the main display (left or right) will not experience the issue. It is always the secondary monitor to the Windows Start Menu.
This issue doesn't happen if I drive external displays using a USB3 Display Link or direct output to secondary screens using TB3. So I think it is related to PD17's support for eGPU. I'm using an AMD Vega 64 in a Razor Chroma eGPU case. This issue also occurred when I was using a Sonnet eGPU case.
 
I'm not using a GPU although I am running through a CalDigit USB-C HDMI Dock.

What I also found is that the issue doesn't occur if I have the taskbar in Windows set to appear on all monitors. If I disable this setting (ie. the task bar is only on the primary monitor), the problem is easily reproducible.

I've reproduced it with a vanilla install of the Windows 10 development free VM that you can create. I've also managed to get support to finally respond to a request and submitted a technical data report to them.

I hope they are now looking into it but am waiting for a response.
 
mbeedub said:
I'm not using a GPU although I am running through a CalDigit USB-C HDMI Dock.

What I also found is that the issue doesn't occur if I have the taskbar in Windows set to appear on all monitors. If I disable this setting (ie. the task bar is only on the primary monitor), the problem is easily reproducible.

I've reproduced it with a vanilla install of the Windows 10 development free VM that you can create. I've also managed to get support to finally respond to a request and submitted a technical data report to them.

I hope they are now looking into it but am waiting for a response.
Click to expand...

Thank you for responding - this is good information and turning the taskbar back on for all displays has solved the issue for me. So this is definitely a bug!
Now I hope to see the money I pay by subscribing to this software every year go to fixing this bug in the latest version of Parallels Desktop 17.

upload_2021-8-26_10-15-49.png
 
That's good to know. Sounds like it is definitely a bug then and not hardware etc related.
Yes let's hope this get's a patch in the next release.
 
You must log in or register to reply here.
Back
Top