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
Same here Edge 110.0.1587.15 on macos 13.1
logs are:
ā macos ./'Microsoft Edge Dev'
objc[20893]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x7ffa5c378550) and /Applications/Microsoft Edge Dev.app/Contents/Frameworks/Microsoft Edge Framework.framework/Versions/110.0.1587.15/Libraries/libGLESv2.dylib (0x10d78b360). One of the two will be used. Which one is undefined.
sysctlbyname for kern.hv_vmm_present failed with status -1Trying to load the allocator multiple times. This is *not* supported.
[bad_variant_access.cc : 44] RAW: Bad variant access
[20881:34051:0121/131133.273182:FATAL:bad_variant_access.cc(44)] Check failed: false. Bad variant access
[0121/131133.994870:WARNING:crash_report_exception_handler.cc(310)] UniversalExceptionRaise: (os/kern) failure (5)
[1] 20881 trace trap ./'Microsoft Edge Dev'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
Edge 110.0.1587.56 Stable still crashes. Microsoft has not fixed the issue adequately
