Edge Version 93.0.961.52 (Official build) (64-bit) issue with Websocket connections

Walter Simonazzi 1 Reputation point


Edge is the standard browser in my organisation. It used to work just fine with an internal mapping web application that displays realtime location data consumed from 2 web-sockets. Performance was always great and all my 20k ( law enforcement) users where very happy with it.

Since the MS Edge update (Version 93.0.961.52 (Official build) (64-bit)), when we turn on the real-time layers (which means Edge needs to make the connection to the web sockets) the whole browser becomes almost unresponsive. Only when we turn off the real-time layers ( Edge unsubscribe from the web socket) the browser turns reponsive again.
Cleaning the cache, force refreshed, etc. did not make any difference.

I have notice that everytime I start the web mapping application and turn on the web socket layers, a service-worker.js file takes all the CPU, which I guess is the reason why the browser becomes unresponsive. snapshot below.
is there anything we can do to avoid this issue?


Microsoft Edge
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
1,574 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. XuDong Peng-MSFT 5,001 Reputation points Microsoft Vendor

    Hi @Walter Simonazzi ,The service worker needs to complete the execution of its event handler within the time limit. In other cases, the browser or operating system may choose to terminate service workers that affect battery, CPU, or memory consumption. I'm not sure if this issue is because the data updated very frequently, I think what you can try is to use Window.requestAnimationFrame() to limit the amount of DOM updates.

    0 comments No comments