Edge browser crashes on Microsoft Editor right-click

Question

When I'm editing text in a field in a web page in Microsoft Edge Version 110.0.1587.69 (Official build) (64-bit), and there's a grammar suggestion underlined by Microsoft Editor, if I right click on the suggestion link, it brings up two popup menus that overlap one another. If I hover the mouse over one of them (I forget which one) it instantly crashes Edge and I lose whatever I've done entering text on that page. I've had similar crashes before, on Feb 7th, when I was using Edge version 109.0.1518.78. My workaround has been to resist the temptation to right click when there's a grammar suggestion - spelling suggestions are safe, and letting it autocomplete sentences by hitting tab is safe. But it's easy to forget to distinguish between spelling suggestions and grammar suggestions, and to right click on a grammar suggestion again - Doh! I'm considering as a workaround switching from Microsoft Editor to the "basic" spell checker under Edge, Settings, Language.

My OS is Windows 10 Enterprise Version 22H2 OS build 19045.2604 with Windows Feature Experience Pack 120.2212.4190.0.

I found someone on Reddit has reported the same bug recently - the only response he's gotten is from me today suggesting he switch to basic spell checker as a workaround.

If I stop using Microsoft Editor, I'm wondering how I will know when this has been fixed and it's safe to use it again.

When the crash happened yesterday, I found these three errors in the Application event log:

---

• <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
• <System> <Provider Name="Windows Error Reporting" /><EventID Qualifiers="0">1001</EventID><Version>0</Version><Level>4</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2023-03-14T21:54:11.0845502Z" /><EventRecordID>170519</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>Application</Channel><Computer>••••••••••.•••.••••••••.com</Computer><Security /></System>
• <EventData> <Data /><Data>0</Data><Data>crashpad_exp</Data><Data>Not available</Data><Data>0</Data><Data>msedge.exe</Data><Data>110.0.1587.69</Data><Data>msedge.dll</Data><Data>110.0.1587.69</Data><Data>69064464</Data><Data>browser</Data><Data>0x80000003</Data><Data>0</Data><Data /><Data /><Data>\?\C:\Users\••••••••••••\AppData\Local\Microsoft\Edge\User Data\Crashpad\temp\a8c21541-d33d-403a-9a85-d97a7114c34f_crashinfo.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB032.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB053.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB071.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0DF.tmp.txt</Data><Data>\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_msedge.exe_8720f7aa174288a7b7b20143379daaed97a52_00000000_cab_93426efc-786c-415d-a733-f2651ff93be5</Data><Data /><Data>0</Data><Data>93426efc-786c-415d-a733-f2651ff93be5</Data><Data>4</Data><Data /><Data>0</Data></EventData> </Event>

---

• <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
• <System> <Provider Name="Windows Error Reporting" /><EventID Qualifiers="0">1001</EventID><Version>0</Version><Level>4</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2023-03-14T21:54:11.1001749Z" /><EventRecordID>170520</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>Application</Channel><Computer>••••••••••.•••.••••••••.com</Computer><Security /></System>
• <EventData> <Data /><Data>0</Data><Data>crashpad_exp</Data><Data>Not available</Data><Data>0</Data><Data>msedge.exe</Data><Data>110.0.1587.69</Data><Data>msedge.dll</Data><Data>110.0.1587.69</Data><Data>69064464</Data><Data>browser</Data><Data>0x80000003</Data><Data>0</Data><Data /><Data /><Data>\?\C:\Users\••••••••••••\AppData\Local\Microsoft\Edge\User Data\Crashpad\temp\a8c21541-d33d-403a-9a85-d97a7114c34f_crashinfo.txt \?\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log</Data><Data /><Data /><Data>0</Data><Data>93426efc-786c-415d-a733-f2651ff93be5</Data><Data>262148</Data><Data /><Data>0</Data></EventData> </Event>

---

• <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
• <System> <Provider Name="Windows Error Reporting" /><EventID Qualifiers="0">1001</EventID><Version>0</Version><Level>4</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2023-03-14T21:54:14.0772220Z" /><EventRecordID>170521</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>Application</Channel><Computer>••••••••••.•••.••••••••.com</Computer><Security /></System>
• <EventData> <Data>0</Data><Data>5</Data><Data>crashpad_exp</Data><Data>Not available</Data><Data>0</Data><Data>msedge.exe</Data><Data>110.0.1587.69</Data><Data>msedge.dll</Data><Data>110.0.1587.69</Data><Data>69064464</Data><Data>browser</Data><Data>0x80000003</Data><Data>0</Data><Data /><Data /><Data>\?\C:\Users\••••••••••••\AppData\Local\Microsoft\Edge\User Data\Crashpad\temp\a8c21541-d33d-403a-9a85-d97a7114c34f_crashinfo.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB032.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB053.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB071.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0DF.tmp.txt</Data><Data>\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_msedge.exe_8720f7aa174288a7b7b20143379daaed97a52_00000000_93426efc-786c-415d-a733-f2651ff93be5</Data><Data /><Data>0</Data><Data>93426efc-786c-415d-a733-f2651ff93be5</Data><Data>268435456</Data><Data>2aea9f515e76e8f7227aa81a2c677edf</Data><Data>0</Data></EventData> </Event>

Answer 1

Hi Rick,

Thank you for your feedback. We can reproduce this issue after testing.

I have submitted your feedback through internal channels to the relevant teams for investigation. To be resolved by the development team in a subsequent version update.

We appreciate your feedback, please click Yes or No to help us improve the support experience. 

Your Sincerely

Hahn - MSFT | Microsoft Community Support Specialist

Answer 2

Do you know when this issue will be fixed in the stable release?

Answer 3

Unfortunately, it seems it's still an issue as of today.

Answer 4

Here's link to it in Feedback: https://aka.ms/AAk0v21

Answer 5

Hi Rick,

Welcome to Microsoft Community.

I'm Hahn and I'm here to help you with your concern.

It seems like you are experiencing a bug with Microsoft Editor in Microsoft Edge browser, which causes the browser to crash when right-clicking on a grammar suggestion. It is also worth noting that you have found a workaround by switching to the basic spell checker.

Based on the event log provided, the following information can be seen.

Event ID 1001 is a Windows error reporting event that reports details of an application crash.

Event log IDs 170519 and 170520 represent two parts of the same error report, respectively.

The error report indicates that the application that crashed was the browser process (msedge.exe) of Microsoft Edge.

The error report also provides information about the location where the crash occurred (msedge.dll), and the version number of the application (110.0.1587.69).

The last line shows the path to the error report file, which includes detailed information about the crash, such as the stack trace and other debugging information.

From the logs, it is not possible to determine exactly which part of the content caused the crash, but it is possible to confirm that Microsoft Edge's browser process crashed while processing syntax suggestions from Microsoft Editor. This may be related to the version of the browser or the version of the Microsoft Editor plugin, and may be a known issue.

Thank you for your feedback. I have submitted this issue to you through internal channels. In addition, you can also submit your problem through the Feedback Hub****(if convenient, please provide as much detail as possible, including pictures, repro videos, etc.).   Please share the feedback link after submitting, I will submit your feedback to the relevant team for investigation through internal channels.

If there is anything not clear, please do not hesitate to let me know.

Your Sincerely

Hahn - MSFT | Microsoft Community Support Specialist