EDGE crashes when delete a Bookmark

Question

Hello,

Edge keeps crashing when you try to delete a favorite. It doesn't matter whether you want to delete it via the favorites management or directly from the favorites list.

Approx. 8-10 seconds after you have deleted a favorite by pressing "Delete", Edge closes immediately. After a restart and a click on Restore, the previously deleted favorite is available again.

It does not matter which favorite you want to delete.

The behavior occurs with a brand new Edge profile. It also does not matter whether the VSE is deactivated or not. Group policies for the EDGE are active or not. It always happens.

Windows 11 version 10.0.22631.3737 Domainmember

Edge version 126.0.2592.81 (official build) (64-bit)

Any idea what else you could try?Dumpfile Snipset:

0:008> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 15

    Key  : Analysis.Elapsed.mSec
    Value: 524

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 4

    Key  : Analysis.Init.CPU.mSec
    Value: 203

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5743

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 619

    Key  : Failure.Bucket
    Value: NULL_POINTER_READ_c0000005_msedge.dll!Unknown

    Key  : Failure.Hash
    Value: {3e2b9b2d-168b-3fa0-d6da-c563857f5d4a}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 5971

    Key  : Timeline.Process.Start.DeltaSec
    Value: 806

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.Process.Version
    Value: 126.0.2592.81


FILE_IN_CAB:  622d15bc-1b58-4dd0-9c8b-c2c95155d635.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=00005cec0a884a80 rbx=00005cec0c087118 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000f9cdfe258 rdi=00005cec0360f418
rip=00007ff8226cf63a rsp=0000000f9cdfdf80 rbp=00005cec0592d180
 r8=00005cec0c1854a0  r9=0000000000000000 r10=00007ff815ec0000
r11=00007ff819da1d41 r12=00005cec0c18dec0 r13=0000000000000000
r14=00005cec0c440db0 r15=00005cec0c440da8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
msedge!argon2_encodedlen+0x30cba8a:
00007ff8`226cf63a 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff8226cf63a (msedge!argon2_encodedlen+0x00000000030cba8a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  msedge.exe

READ_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

STACK_TEXT:  
0000000f`9cdfdf80 00007ff8`226cdfca     : 0000000f`9cdfe390 00007ff8`1f47ef8b 00a778f0`1a07a6e7 00005cec`0c401200 : msedge!argon2_encodedlen+0x30cba8a
0000000f`9cdfe0e0 00007ff8`21ebc935     : 00005cec`03c16085 00005cec`03c160ab 00000000`0004eb05 00005cec`03c160ab : msedge!argon2_encodedlen+0x30ca41a
0000000f`9cdfe2d0 00007ff8`21eb07f0     : 00000000`0000026b 0000000f`9cdfeb98 0000000f`9cdfe9d0 00000001`63e876b8 : msedge!argon2_encodedlen+0x28b8d85
0000000f`9cdfe450 00007ff8`21ebbe49     : 0000000f`9cdfec00 00005cec`052ff5c8 00005cec`08b14630 00007ff8`19d46f3f : msedge!argon2_encodedlen+0x28acc40
0000000f`9cdfe4c0 00007ff8`21ebc290     : 00000000`00000000 00000000`00000000 00000000`00000000 00000001`63e87683 : msedge!argon2_encodedlen+0x28b8299
0000000f`9cdfe790 00007ff8`21ec5cb4     : efcdab89`67452301 00000000`00000018 0000000f`9cdfef08 00007ff8`254bceb0 : msedge!argon2_encodedlen+0x28b86e0
0000000f`9cdfe800 00007ff8`21210b71     : 00005cec`07720de0 00005cec`07720df8 aaaaaaaa`aaaaaa01 00000000`00000000 : msedge!argon2_encodedlen+0x28c2104
0000000f`9cdfee20 00007ff8`21210214     : 00007ff8`00000040 00007ff8`17189cd5 00000000`00000000 00000000`00000000 : msedge!argon2_encodedlen+0x1c0cfc1
0000000f`9cdff0a0 00007ff8`2120c107     : 0000000f`9cdff410 00000000`00000000 0000e728`05780ce6 0000e728`05780fd6 : msedge!argon2_encodedlen+0x1c0c664
0000000f`9cdff270 00007ff8`2120dfeb     : 00000000`00000000 00000000`00000040 00005cec`04e2a200 00005cec`00a7e9a0 : msedge!argon2_encodedlen+0x1c08557
0000000f`9cdff460 00007ff8`16b353e2     : 00000000`0000003e 00007ff8`174a92e0 00000000`00000040 00007ff8`16de0c78 : msedge!argon2_encodedlen+0x1c0a43b
0000000f`9cdff5f0 00007ff8`16b3514c     : 00005cec`08ab778d 00007ff8`16b3733f aaaaaaaa`aaaaaaaa 00005cec`036e2f40 : msedge!IsSandboxedProcess+0x516942
0000000f`9cdff690 00007ff8`16b35224     : 80000000`00000030 0000e728`05780b76 0000000f`9cdff768 00007ff8`160c4963 : msedge!IsSandboxedProcess+0x5166ac
0000000f`9cdff720 00007ff8`16b33ff4     : aaaaaaaa`aaaa0001 00000001`63e849a6 aaaaaaaa`aaaa0002 0000e728`05780a96 : msedge!IsSandboxedProcess+0x516784
0000000f`9cdff790 00007ff8`160fc5b7     : 00003c8c`00000000 00007ff8`16de0c78 00003c8c`00294480 0000000f`9cdffc30 : msedge!IsSandboxedProcess+0x515554
0000000f`9cdffb70 00007ff8`16185fd8     : 0000e728`057801a6 00007ff8`16185ec1 00003c8c`00383ba0 00003c8c`003f8680 : msedge+0x23c5b7
0000000f`9cdffcd0 00007ff8`17318870     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge!ChromeMain+0x19478
0000000f`9cdffd10 00007ff8`bffe257d     : 00000050`00000030 00000000`00000000 00000000`00000000 00000000`00000000 : msedge!IsSandboxedProcess+0xcf9dd0
0000000f`9cdffda0 00007ff8`c080af28     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d
0000000f`9cdffdd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


STACK_COMMAND:  ~8s; .ecxr ; kb

SYMBOL_NAME:  msedge+30cba8a

MODULE_NAME: msedge

IMAGE_NAME:  msedge.dll

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_msedge.dll!Unknown

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  126.0.2592.81

Answer 1

Hi @Zacharias Embaxter

This is a known issue and Edge team has implemented a code change to address the issue.

It is planned to release a fix for this issue in the next update for Microsoft Edge Stable, which is currently scheduled for the week of 01 July 2024. Let's wait for the new release in the future.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Regards,

Yu Zhou