Edge browser crash - EEAP - 16241.1001.170708-1800

Not reproducible Issue #13012618

Details

Author
vivek s.
Created
Jul 31, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Win10 version on which issue was seen:-

16241.1001.170708-1800.rs_prerelease_CLIENTPRO-CORE_OEMRET_X64FRE_en-US

We see Edge browser crashing while accessing our parts of our extensions.

Our extension is a java script extension and assumption is, it should not take crash the Edge browser as such.

Will add more analysis and steps to reproduce soon.

Stack Trace:-

FAULTING_IP:
Windows_UI!Ordinal1700+da8a
00007ffb`517261ca 488b4018 mov rax,qword ptr [rax+18h]

EXCEPTION_RECORD: ffffffffffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ffb517261ca (Windows_UI!Ordinal1700+0x000000000000da8a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00007ffb00011419
Attempt to read from address 00007ffb00011419

CONTEXT: 0000000000000000 – (.cxr 0x0;r)
rax=00007ffb00011401 rbx=000000522c4fda70 rcx=000001f1e82fcf30
rdx=00007ffb51727920 rsi=000000522c4fd580 rdi=000000522c4fd580
rip=00007ffb517261ca rsp=000000522c4fdca0 rbp=000001f1dca20178
r8=000001f1e82fd290 r9=0000000000000030 r10=00000fff6a2e7c6c
r11=5555555155155555 r12=0000000000000000 r13=000001f1e97fbb58
r14=000001f1e97fba70 r15=000001f1dca20180
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010204
Windows_UI!Ordinal1700+0xda8a:
00007ffb517261ca 488b4018 mov rax,qword ptr [rax+18h] ds:00007ffb00011419=???

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

PROCESS_NAME: MicrosoftEdge.exe

ADDITIONAL_DEBUG_TEXT:
You can run ‘.symfix; .reload’ to try to fix the symbol path and load symbols.

FAULTING_MODULE: 00007ffb63f90000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP: 15b6ce90

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00007ffb00011419

READ_ADDRESS: 00007ffb00011419

FOLLOWUP_IP:
Windows_UI!Ordinal1700+da8a
00007ffb`517261ca 488b4018 mov rax,qword ptr [rax+18h]

APP: microsoftedge.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS

BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 00007ffb51724dbf to 00007ffb517261ca

STACK_TEXT:
000000522c4fdca0 00007ffb51724dbf : 0000000000000000 000001f1dca20170 000001f1e82fd1a0 000001f1e82fd170 : Windows_UI!Ordinal1700+0xda8a
000000522c4fdcd0 00007ffb5170a423 : 000001f1e5c1db60 000001f1e97fba70 00007ffb5177d690 00007ffb5177d690 : Windows_UI!Ordinal1700+0xc67f
000000522c4fdd40 00007ffb5171a964 : 000001f1e82fd170 000001f1dca1fce0 0000000000000000 0000000000000000 : Windows_UI!Ordinal1690+0xa423
000000522c4fdd70 00007ffb633e8623 : 000001f1e97fba70 0000000000000001 000000522c4fe458 00007ffb5171a650 : Windows_UI!Ordinal1700+0x2224
000000522c4fdf90 00007ffb6344b97c : 00007ffb63e5c3d0 000000522c4fe450 00007ffb5ca7b1b0 00007ffb63e5c3d0 : rpcrt4!NdrInterfacePointerMemorySize+0x1133
000000522c4fdfe0 00007ffb633a7519 : 000000522c4fe710 0000000000000000 00007ffb63e4fe78 00007ffb63cb22fe : rpcrt4!NdrClientCall3+0x479c
000000522c4fe6a0 00007ffb63caec4f : 0000000000000000 000000522c4fe8d0 00007ffb5ca7b1b0 000001f1df6a62d0 : rpcrt4!NdrStubCall3+0xc9
000000522c4fe700 00007ffb633d2f1b : 0000000000000001 0000000000000000 000001f1e627f900 0000bb6d44d47ec2 : combase!CStdStubBuffer_Invoke+0x7f
000000522c4fe740 00007ffb63cb27e3 : 000001f1e59713e0 0000000000000000 0000bb6d44d47f12 00007ffb63fbdcea : rpcrt4!CStdStubBuffer_Invoke+0x3b
000000522c4fe770 00007ffb63cb25ae : 000001f1dc6f2c10 000000522c4fe850 000000522c4fe810 000001f1dc5b09a0 : combase!NdrExtStubInitialize+0x3833
000000522c4fe7d0 00007ffb63cafe8e : 000001f1e627f9f8 000000522c4fea80 000001f1df6a62d0 00007ffb517a5be8 : combase!NdrExtStubInitialize+0x35fe
000000522c4fe920 00007ffb63d15754 : fffffffffffffffe 000000522c4fefa8 000001f1dc669e50 0000000000000000 : combase!NdrExtStubInitialize+0xede
000000522c4fed20 00007ffb63cb6bad : 0000000000000000 000001f1e627f970 000000522c4fef90 000000522c4fefb0 : combase!Ordinal69+0x8d4
000000522c4fef00 00007ffb63cb359d : 000001f1dc6c3e60 000001f1d0908070 000001f1df6a62d0 000001f1e97fba70 : combase!CoCreateInstance+0x2dbd
000000522c4ff000 00007ffb63cab0aa : 000001f1e627f970 0f4420f000009c06 9d7cc26e7496ecb6 000001f1e5e96df0 : combase!NdrExtStubInitialize+0x45ed
000000522c4ff2d0 00007ffb63cf5059 : 0000000000000006 000001f1df6fa160 000000522c4ff790 000000522c4ff738 : combase!NdrCStdStubBuffer_Release+0x9ca
000000522c4ff3a0 00007ffb63cfadc8 : 000001f1df6fa170 000000522c4ff790 000000522c4ff790 000000522c4ff790 : combase!CoGetStandardMarshal+0x1ef9
000000522c4ff3f0 00007ffb63cfccd9 : 0000000000000000 0000000000000000 0000000000000070 000001f1dc6c3e60 : combase!RoGetAgileReference+0x14a8
000000522c4ff6d0 00007ffb51729df4 : 0000000000000000 00007ffb00000000 000001f1dca18b80 0000000000000000 : combase!Ordinal87+0xb9
000000522c4ff730 00007ffb5172bdab : 00007ffb517fc000 000001f1dca18b80 0000000000000000 0000005200000000 : Windows_UI!Ordinal1700+0x116b4
000000522c4ff840 00007ffb42d9d4ec : 000001f1dc6c2ef0 0000000000000000 00007ffb5c561170 0000000000000000 : Windows_UI!Ordinal1700+0x1366b
000000522c4ff8f0 00007ffb42d9d490 : 000001f1dca18b80 00007ffb42c3ea8e 0000000000000000 0000000000000000 : Windows_UI_Xaml!DllGetActivationFactory+0x20eecc
000000522c4ff920 00007ffb5c43bdda : 0000000000000001 000001f1dca18550 000000522c4ffa00 00007ffb5c561170 : Windows_UI_Xaml!DllGetActivationFactory+0x20ee70
000000522c4ff990 00007ffb5c471caf : 000001f1dca17150 00007ffb5c561170 0000000000000000 0000000000000000 : twinapi_appcore!Ordinal6+0x2baa
000000522c4ff9c0 00007ffb62f7d6e5 : 000001f1dca17150 00000000000020f0 000001f1dca17150 000001f1dca054c0 : twinapi_appcore!PsmInitializeExtension+0x58df
000000522c4ffa40 00007ffb639962b4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : SHCore!Ordinal247+0x1b5
000000522c4ffb20 00007ffb63f98c61 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
000000522c4ffb50 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: windows_ui!Ordinal1700+da8a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Windows_UI

IMAGE_NAME: Windows.UI.dll

STACK_COMMAND: ~10s; .ecxr ; kb

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS_c0000005_Windows.UI.dll!Ordinal1700

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:wrong_symbols_c0000005_windows.ui.dll!ordinal1700

FAILURE_ID_HASH: {c18d6a16-68e5-60db-697e-9b739999a5f2}

Followup: MachineOwner

Attachments

0 attachments

    Comments and activity

    • Correcting the typos in the defect description:-

      Win10 version on which issue was seen:-
      16241.1001.170708-1800.rs_prerelease_CLIENTPRO-CORE_OEMRET_X64FRE_en-US

      We see Edge browser crashing while accessing parts of our extensions.

      Our extension is a java script extension and assumption is, it should not crash the Edge browser as such.

      Will add more analysis and steps to reproduce soon.

    • Microsoft Edge Team

      Changed Status to “Fixed”

      Changed Status from “Fixed” to “Not reproducible”

    You need to sign in to your Microsoft account to add a comment.

    Sign in