[Win11] MS Edge **hangs** instantly in "Menu > Help and comments > Send a comment". Need to kill the process. #759
Replies: 2 comments
-
Due to this bug, I cannot report it normally to Microsoft, which suggests using the "Send a comment" button of Edge itself. |
Beta Was this translation helpful? Give feedback.
-
I have the same bug when running Edge in Windows 11 Pro installed in a VM (hosted on Windows within Hyper-V, or on all tested Linux distribs, based on RedHat, Fedora, or Ubuntu, within KVM or within VirtualBox): this does not hangs the VM or the hypervisor, the bug only affects all running Edge processes, which hang the same way on the virtual desktop. So this is definitely not a hardware problem. Clearing all caches, reinstalling Edge has no effect (Windows 11 is up to date on all tested devices and VMs). I have also tested on a Windows 10 device: we get the same hang. The "Send a comment" feature in MSEdge for Windows is broken everywere! (I have still not tested if this also affects MSEdge for Linux, or MSEdge for Android; I cannot test MSEdge for MacOS). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Any attempt in MsEdge (currentt release, or current beta) on Windows 11 to "send a comment" via the dedicated buttons in the UI, (or from the top menu) instantly hangs Edge.
Which becomes UNRESPONSIVE, stops all rendering, the window cannot be resized,, all the UI is frozen. We have to use the red "[x]" button to close it, which displays that Edge is not responding, and we can only kill the process.
"Send a comment" has a severe bug, in all current versions of Edge (official release, or current Beta), on various versions of Windows 11.
This may be caused by "strict" privacy settings. The bug also occurs when running Edge in "Private mode".
Apparently this button attmpts to open a remote HTTPS session which is blocked somewhere, or but trying to violate the existing privacy policis in some internal extensions that expects to receive a response or is not prepared to get an access error from the API (possible uncaught exception).
This is VERY EASY to reproduce on multiple PC devices, running various version of Windows 11 (Home, Pro) in any branch (Retail, Insider Beta, Insider Canary...), and with any existing branch of MSEdge for Windows. Disabling all plugins also has NO effect on this bug.
Beta Was this translation helpful? Give feedback.
All reactions