Edge Beta crashing as of Jan 20, 2023 after update i guess

[Dave_Gleason_DGNorCal]

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. Firefox isn't crashing either.  I have searched high and low but don't see anything out there.  I will just use another browser for now and wait to see if things change in a couple of days.  

I guess this is more of an FYI

[#2]

Same here, on Beta Version 110.0.1587.17, just closes after about 10 minutes, no matter how many tabs are open. Windows 11 Pro x64

[#3]

@Dave_Gleason_DGNorCal 

Exactly the same here, every 10 minutes almost on the dot.

Windows 10 Education 22H2

[#4]

Version 110.0.1587.17 (Official build) beta (64-bit)
Crashing constantly. I've tried repairing multiple times to no avail.

Windows 11 Pro 64 Bit

[#5]

HOUSTON: it looks like we have a problem.  Thanks to you all who have confirmed. I was starting to think my gray noodle was beyond repair also.  Nothing helps. Finally just switched browsers for now.

@TriciaP 

[#6]

I have seen the same thing happening with Edge Dev and it started last night - 1/20. Just closed after some time - no warning and no messages.

[#7]

Version 110.0.1587.17 (Official build) beta (64-bit) also crashes regularly.

[#8]

I see the same issue here with it just open

[#9]

Same here with 110.0.1587.15 (Dev) on Mac (Ventura 13.2).

[#10]

I notice other commenters are on Windows. Can confirm this is happening on OSX as well.
Edge Dev Version 110.0.1587.15 (Official build) Dev (x86_64)
OSX is Big Sur 11.7.2 - nothing latest greatest.
It seems to have started around the 20th for me as well. (Haven't used this specific laptop heaviliy. But I will add, I have Edge Dev on my work laptop (Win 10) and I do NOT observe this behavior.)
I have noticed it mostly when I leave the computer and come back it's not running and when I re-launch it prompts to restore tabs. However, I did just observe the "10 minute" thing - although I was not precisely timing but that seems reasonable.
Amazing how annoying something like this becomes having been stable for so long even on dev channel - it's my daily driver.
Thanks!

[#11]

@Dave_Gleason_DGNorCal 

Same here. Crashed exactly as I was clicking the Like button on your post. 😉 110.0.1587.17 beta arm64 macOS Ventura 13.1

[#12]

@Dave_Gleason_DGNorCal 

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'

[#13 · Accepted solution]

@AndreStanko 

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

[#14]

Same here

[#15]

Same here on Version 110.0.1587.17 (Official build) beta (64-bit), Win 11 22H2, crashes every 10 minutes or so.

[#16]

Same here on Beta 110.0.1587.17. I wonder if there is a guide to quickly rollback to a previous version? This seems very usable.

[#17]

Having same from yesterday just crashing after 10 mins @Dave_Gleason_DGNorCal 

[#18]

I'm guessing there's an internal ping every 10 minutes to telemetry or experiment or server or something that is failing and doesn't exit gracefully

[#19]

Same 110.0.1587.17 version same crashing issues '-'

[#20]

@Dave_Gleason_DGNorCal Same here - about ten minutes too. Is it going to be fixed?