Forum Discussion
Solved
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....
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
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?
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.The workaround appears to work for me (windows 10) I tried it the first time then closed it after 35 mins, rebooted a little later without using the workaround and I'm into 45 mins plus now.
- Eric_Lawrence
Microsoft
Disabling the features temporarily is harmless and you're unlikely to notice any difference.
In /theory/, the buggy code has already been disabled by experimental config flags from the server (see https://textslashplain.com/2019/07/16/updating-browsers-quickly-flags-respins-and-components/#:~:text=using%20OmahaProxy.-,Field%20Trial%20Flags,-In%20some%20cases) which means you shouldn't need the command line arguments any longer.- It's still crashing for me. Do I need to manually update it or something?
