Forum Discussion
Dave_Gleason_DGNorCal
Jan 21, 2023Iron Contributor
Edge Beta crashing as of Jan 20, 2023 after update i guess
Edge Beta is crashing after 5 to 10 minutes of opening. Started Jan 20, 2023 late. Disabled the Edge WinView2 or whatever that is but didn't help. I have Edge standard open and there are no issues....
- Jan 21, 2023
I got this lovely message in WinDbg
seems to be a bug with old Microsoft's telemetry client accessing memory it shouldn't be hmmm.
STACK_COMMAND: ~9s; .ecxr ; kb SYMBOL_NAME: msedge+1990790 MODULE_NAME: msedge IMAGE_NAME: msedge.dll FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_msedge.dll!Unknown OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 110.0.1587.17 FAILURE_ID_HASH: {c171bb6a-7522-ae2f-5ecb-19c1b53d3623} Followup: MachineOwner --------- 0:009> ExceptionAddress: 00007ff9125e2ca0 (msedge!telemetry_client::IDataFieldVisitor::IDataFieldVisitor+0x0000000001990790) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000
Daniel Baird
Jan 23, 2023Copper Contributor
I'm afraid "msedge.exe --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryService" did not work for me 😞
Eric_Lawrence
Microsoft
Jan 23, 20231. You confirmed that there were no msedge.exe processes in Task Manager before running, right?
2. Can you please share an Uploaded Crash Report ID # from your edge://crashes page?
2. Can you please share an Uploaded Crash Report ID # from your edge://crashes page?
- Daniel BairdJan 23, 2023Copper Contributor
It crashed one more time, but does seem more stable now.... crash report below:
{
"Local ID": "c20665df-6bff-47e2-94a1-bdaa55a89abe",
"Upload ID": "c20665df-6bff-47e2-94a1-bdaa55a89abe",
"Bucket ID": "1d6f27b21353eae95db75eba16cd3452",
"Cab ID": "",
"Capture Time": "Monday, 23 January 2023 at 15:05:16",
"Upload Time": "Monday, 23 January 2023 at 15:05:16",
"State": "Reported",
"P1": "msedge.exe",
"P2": "110.0.1587.17",
"P3": "msedge.dll",
"P4": "110.0.1587.17",
"P5": "123677856",
"P6": "browser",
"P7": "0xc0000005",
"P8": "0"
}- Eric_LawrenceJan 23, 2023
Microsoft
Thanks. I've confirmed that your crash ID matches the known issue that we're tracking and fixing. The workaround has been effective for other folks that have tried it. The one known reason why it wouldn't work is if you already had an Edge instance in the background (because Edge only respects arguments passed to the very first instance). You can verify whether your current browser "sees" the argument by looking for it on the edge://version page as described in https://textslashplain.com/2022/01/05/edge-command-line-arguments/#:~:text=An%20argument%20I%20tried%20didn%E2%80%99t%20seem%20to%20do%20anything%3F%20Why%20not%3F