Forum Discussion
Edge 128.0.2739.42 crashes when user clicks on custom URI
We have a small custom app to allow us to open file links from our intranet site. We created a custom uri handler and it has been working up until Edge Version 128.0.2739.42 . With version 128 clicking the file links crashes all edge windows with no error messages in the event viewer. We can open the links in a new tab/window via right click or ctrl/shift clicks. This issue occurred with both Windows 10 and 11. Also crashes on Canary as of 8/26.
Examples (edited to protect the innocent):
Standard link url:
<a href="CustomApp:\\UNCNetworkPath\DirA\SubA\SubB\AwesomeFile.pdf " target="_blank" > AwesomeFile.pdf</a>
The URI was registered via registry settings:
[HKEY_CLASSES_ROOT\CustomApp]
@=URL:Custom%20File%20Protocol
"URL Protocol"=""
[HKEY_CLASSES_ROOT\CustomApp\shell]
[HKEY_CLASSES_ROOT\CustomApp\shell\open]
[HKEY_CLASSES_ROOT\CustomApp\shell\open\command]
@="C:\\Program Files\\CustomApp\\CustomApp.exe %1"
In 128 after analyzing the file with Windbg the failure bucket is:
Key : Failure.Bucket
Value: BREAKPOINT_80000003_msedge.dll!content::NavigationURLLoaderImpl::CreateThrottlingLoaderAndStart
And Exception Record:
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007fffa57f002b (msedge!content::NavigationURLLoaderImpl::CreateThrottlingLoaderAndStart+0x0000000000000281)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
PROCESS_NAME: msedge.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
EXCEPTION_PARAMETER1: 0000000000000000
Any ideas on what might be causing this?
- I've just fixed (cludged!) our issues by changing all hyperlinks and window.open statements which call our custom protocol so that they use a target of '_self' . Some used '_blank', others didn't specify anything.
Everything's now working.
However - for Microsoft / Google if you're reading - this is a workaround and the underlying problem needs to be fixed.
7 Replies
- Bug is being triaged now by Chromium developer 🤞
https://issues.chromium.org/issues/361600654#comment26 THaack
We have the same problem in our company.
The two common conditions of the PCs that are having the problem are.- They are logged into Windows with a M365 account.
- They are using the version 128 of Edge.
The version 127 of Edge did not cause the problem in the environment where a user logs in with his M365 account. After updating to 128, he gets the same problem.
The same problem occurs with latest Google Chrome (ver.128) in our environments where the problem of Edge occurs, but not with FireFox.Updated:
Our protocol handler is listed in a "URL Allow list" which is distributed as a InTune policy. The problem can be avoided by changing the protocol name in the list.
https://support.google.com/chrome/a/thread/292536913?hl=en&msgid=293182926- I've just fixed (cludged!) our issues by changing all hyperlinks and window.open statements which call our custom protocol so that they use a target of '_self' . Some used '_blank', others didn't specify anything.
Everything's now working.
However - for Microsoft / Google if you're reading - this is a workaround and the underlying problem needs to be fixed.
I have found that if you remove target="_blank" you can work around the issue.
THaack we have exactly this same behaviour, started yesterday after the upgrade to 128.0.2739.42.
We have a custom protocol to enable us to open a client side app from the browser, and it's been working perfectly until yesterday. Now when someone clicks a link which uses that protocol Edge closes automatically, and upon restarting offers us the chance to restore.
I haven't yet tested the right-click to see if that works but a temporary workaround for now has been to use IEMode for a particular URL path but we need a fix for the actual problem. Interesting Chrome - which also updated yesterday - works perfectly, as does Firefox.
You can use GP to rollback to edge 127 as well. That's what we've done.
https://learn.microsoft.com/en-us/deployedge/edge-learnmore-rollback
