Forum Discussion
Edge Beta crashing as of Jan 20, 2023 after update i guess
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
Microsoft
Sorry for the inconvenience. The fix should be released shortly. Until then a workaround may be:
- Close all instances (verify in task manager)
- msedge.exe --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryService
If that doesn’t help, please retreat to the stable channel.
- Unfortunately that won't work on MacOS, do you have an alternative for Monterey?
- Eric_Lawrence
To pass arguments on Mac, use Terminal to launch.
1. Verify all instances are closed in Activity Monitor (or whatever Mac task manager)
2. Run/Applications/Microsoft\ Edge\ Beta/Contents/MacOS/Microsoft\ Edge\ Beta --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryServiceEric_Lawrence disabling the features as you suggested worked for me. thanks!
- The issue, crashing after 5 - 10 minutes, is present on MacOS Monterey version 110.0.1587.15
- I'm afraid "msedge.exe --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryService" did not work for me 😞
- Eric_Lawrence1. 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?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"
}
- Thank you. This worked for me.
I confirm that it did work for me 🙂
Thank you!
This solution worked fine for me.
All Edge instances (including the stable channel) must be closed before to add parameters to the shorcut target on the start menu.
Thank you.
Hope they'll publish an upgraded fixed build via windows update soon.
- Is there a planned generated Beta build being pushed out today or tomorrow?
- Thanks, but I tried another browser, and that works fine, I will use that from now on. It was a mess anyway to login with my Microsoft account on this forum 😞
- This worked for me.
I did, however start a terminal in the edge beta directory and started it that way
C:\Program Files (x86)\Microsoft\Edge Beta\Application
RUnning now for several hours without crash 🙂 Thanks for the update.
I'm currently testing this workaround, will update shortly with results.
I've edited my shortcut and verified the arguments get passed
- That's exactly what I did and finally some peace of mind.
Now, when would it be time to change it back, and will we ever remember to do so?- next version release I presume.
I hope I remember. Question is, what does disabling these features actually break and are they actually important? 😉
All seems to be working however.
