Forum Discussion

josh_bodner's avatar
josh_bodner
Icon for Microsoft rankMicrosoft
Jun 15, 2021

Dev channel update to 93.0.916.1 is live

Hello Insiders!  Today we’re releasing build 93.0.916.1 to the Dev channel.  Alongside this, we’re excited to announce a campaign to spur extension development and usage:  https://techcommunity.micro...
Kent Herring's avatar
Kent Herring
Brass Contributor

Hi, is anyone else having memory type error messages using Edge Dev?  Only recently I've started to get various messages:  "Error code: Out of Memory"; "RESULT_CODE_HUNG"; SBOX_FATAL_MEMORY_EXCEEDED"?   I get a variety of messages when I try to open Google's calendar, and other websites.  When I click within Amazon this happens.  These errors do not happen within Edge Stable.  Only recently this started happening.  I've checked memory (16GB Ram); closed everything else out, and still get these messages.   I feel like it is something within Dev.  I get the same result with Dev In Private mode.   I've reset Edge Dev, deleted history, cookies, etc., and still get these errors.  Set all Flags to default.   No changes.  Otherwise my machine is acting normally and so is Edge Stable.   The error codes seem to come from certain pages - not all.   So maybe something specific within Dev that changed recently?   Even when the page says "Out of Memory", Task Manager does not show a resource issue. Using Windows Defender, no 3d party anti-virus, and also tried with all extensions disabled.    Thanks, Kent

  • Woody Woodman (WOODY)'s avatar
    Woody Woodman (WOODY)
    Icon for Microsoft rankMicrosoft
    Jun 17, 2021

    abdelfattah 

    So, I have one error: 

     

    - Histogram: Microsoft.Accessibility.UIAClient recorded 1 samples (flags = 0x41)

    612857738  -O                                                                        (1 = 100.0%)

     

    BUT the recorded number doesn't increase with further invocation of that YouTube example (https://www.youtube.com/watch?v=0mGhhdPgXG8)

    Once that Youtube tab has hung, F12 is not operational (works on other open tabs, but not this one).

    msedge.exe --disable-renderer-accessibility had no effect.

     

    Edgecrash did auto upload I see (upload ID d20b808e-73fc-4297-a845-b8a2aa0c2fd6)

    • Eric_Lawrence's avatar
      Eric_Lawrence
      Icon for Microsoft rankMicrosoft
      Jun 17, 2021

      Woody Woodman (WOODY) - The 612857738 value indicates that the browser has Accessibility Mode turned on because you've got the Text Cursor Indicator feature enabled in Windows. This datapoint is written only once when the browser initially starts up-- it won't go higher than 1 with each page you load, for instance.

       

      The supplied command line will turn off accessibility and prevent the crash/hang. If you don't see it working, the 99.9% likelihood issue is that there was already an msedge.exe instance running, so the command line was ignored when you launched the new one. You need to use Task Manager to ensure all msedge.exe instances are closed. You can then verify in your new browser instance that the edge://histograms/UIA that Accessibility Mode is no longer getting enabled by UIA, and your hangs will go away.

  • Eric_Lawrence's avatar
    Eric_Lawrence
    Icon for Microsoft rankMicrosoft
    Jun 16, 2021

    It is indeed very likely to be the same bug that we had inherited from upstream. 93.923, currently in Canary, has the fix. The fix should be in the next Dev build. Sorry for the inconvenience.

    (As an aside, the Upload ID from the edge://crashes page is helpful for us to be able to look at the specific details of any crashes encountered).

Resources