Console is stuck in Chrome v142 (Mac with Intel) | Need to quit chrome after this

[sreenme1]

Describe the bug

Console is stuck in and the Chrome browser freezes. User is forced to quit Chrome and reopen it.
This is seen since last 2 weeks. Chrome v142 was released on Oct 28th and it has some changes related to webgpu.

Ref: https://developer.chrome.com/blog/new-in-webgpu-142

Issue is seen only in users having Mac with Intel and in Chrome browser v142.
(Issue is not seen in Mac with Apple silicon)
We tried downloading an old version of Chrome - v140 - This works. Issue happened after v142 upgrade.

Note: When I try disabling the option ‘Use graphics acceleration when available’ in chrome and relaunch - no issues are seen in v142.

To reproduce
Steps to reproduce the behavior:

1. Go to console
2. Canvas is stuck and connecting text sometimes moves up and down and the browser is stuck

Expected behavior
Console should work fine in all latest and supported versions of all browsers.

Screenshots

Client (please complete the following information):

• OS: [e.g. iOS] - Mac with Intel (Issue is not seen in Mac with Apple)
• Browser: [e.g. chrome, safari] - Chome
• Browser version: [e.g. 22] 142

Server (please complete the following information):

• noVNC version: [e.g. 1.0.0 or git commit id] - 1.6.0
• VNC server: [e.g. QEMU, TigerVNC]
• WebSocket proxy: [e.g. websockify]

Additional context
Add any other context about the problem here.

[CendioZeijlon]

@CendioOssman, @samhed Have you seen this behavior recently?

[samhed]

@CendioOssman, @samhed Have you seen this behavior recently?

Nope, but I rarely use Mac.

[CendioOssman]

It unfortunately sounds like a Chrome bug that we probably can't do much about. Have you reported the issue to Chrome, @sreenme1?

[sreenme1]

Hi @CendioOssman

I am not sure if they will accept this. Based on the release notes, I felt that they have made the changes based on some of the past issues which have been reported in Intel based Mac's + Chrome. Intel folks and Chrome team had worked together on this.
So, I was thinking whether this will need any changes from novnc side to handle this

[CendioOssman]

I don't quite understand what you mean. I would assume that Chrome would still want their browser to work on Intel Macs. And that they want to be able to use hardware acceleration.

noVNC is in the end just a web page. This issue is likely happening on other pages as well.