none
Access Violation from clr!GetMetaDataInternalInterface RRS feed

  • Question

  • Hi,

    My managed WCF application running as Windows service crashes intermittently. When tried to get the crash dump, got Access Violation coming from clr!GetMetaDataInternalInterface. Top of the call stack for the faulting thread is as below:

    000000000df7d548 000007fefd1b940d KERNELBASE!RaiseException+0x39, calling ntdll!RtlRaiseException
    000000000df7d580 000007fef91145f1 clr+0x45f1, calling clr+0x1320
    000000000df7d5b0 000007fef94648f6 clr!GetHistoryFileDirectory+0xe6846, calling clr+0x1320
    000000000df7d5d0 0000000077231256 ntdll!KiUserExceptionDispatch+0x3c, calling ntdll!RtlRestoreContext
    00000002538c4150 0000000000000000 0000000000000000 ====> Exception cxr@000000000df7d5e0
    000000000df7d5e0 000007fef91a865c clr!GetMetaDataInternalInterface+0x3a13c, calling clr!GetHistoryFileDirectory+0xe680c
    000000000df7d610 000007fef91a86aa clr!GetMetaDataInternalInterface+0x3a18a, calling clr!GetMetaDataInternalInterface+0x3a130
    000000000df7d8e0 000000007700b292 kernel32!GetThreadTimes+0x32, calling ntdll!NtQueryInformationThread

    000000000df7d900 000007fe9a5a8e36 (MethodDesc 000007fe99e43480 +0x116 ApplicationCode.ServiceLibraryCommon.CouchbaseSnapshotStore.GetSnapshot(ApplicationCode.ServiceLibraryCommon.RequestContext, Int32, UInt32 ByRef)), calling 000007fe999e0660

    .....

    .....

    The code is compiled with .net 4.5.2 and is executing on Windows 2008 server with .net 4.5.2 installed. Can someone please help me get beyond the clr!GetMetaDataInternalInterface call so as to better understand the cause of AV?

    Thanks,

    Shweta

    • Moved by Fred Bao Tuesday, December 30, 2014 7:06 AM WCF Related
    Monday, December 29, 2014 8:02 PM

All replies

  • Hello,

    It seems this issue is related with WCF application, i move it to the WCF forum for getting better help.

    The current forum you posted to is used to discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection.

    Regards.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, December 30, 2014 7:04 AM
  • Hi Fred,

    From the crash dump call stack, the crash seems to be coming from clr!GetMetaDataInternalInterface and there isn't much available online about GetMetaDataInternalInterface, hence I had posted the question in .Net Framework forum. Not sure if this has anything to do with the application being WCF.

    00000002538c4150 0000000000000000 0000000000000000 ====> Exception cxr@000000000df7d5e0
    000000000df7d5e0 000007fef91a865c clr!GetMetaDataInternalInterface+0x3a13c, calling clr!GetHistoryFileDirectory+0xe680c

    Thanks,

    Tuesday, December 30, 2014 3:49 PM
  • Thanks LemonStreet. I looked into the two links but am not able to correlate to my issue. Mine is purely managed application with only P/Invoke to WINAPI GetThreadTimes which I already inspected and ruled out as culprit. The process crashes if debugger is not attached with event:

    Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9826450 (000007FEF9610000) with exit code 80131506

    Here's !analyze -v output.

    FAULTING_IP: 
    KERNELBASE!RaiseException+39
    000007fe`fd5a940d 4881c4c8000000  add     rsp,0C8h

    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fefd5a940d (KERNELBASE!RaiseException+0x0000000000000039)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000008
    Attempt to read from address 0000000000000008

    CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
    rax=00000000c60e4a23 rbx=000000000000000e rcx=000000000348c850
    rdx=000007fef6a89fd0 rsi=0000000000000048 rdi=00000000777fd788
    rip=000007fefd5a940d rsp=000000000348ce60 rbp=000000000348cf90
     r8=0000000000000000  r9=0000000000000000 r10=000007fe9aa0437e
    r11=000000000348cea0 r12=00000003fcf31fd8 r13=0000000436d51ba0
    r14=0000000436d55ed8 r15=0000000082cda030
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000200
    KERNELBASE!RaiseException+0x39:
    000007fe`fd5a940d 4881c4c8000000  add     rsp,0C8h

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    PROCESS_NAME:  Application.WindowsService.exe

    OVERLAPPED_MODULE: Address regions for 'Castle_Core' and 'Ninject.Extensions.Factory.dll' overlap

    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:  0000000000000008

    READ_ADDRESS:  0000000000000008 

    FOLLOWUP_IP: 
    clr!GetMetaDataInternalInterface+3a13c
    000007fe`f96a865c cc              int     3

    Please let me know if there's any other more appropriate forum to follow-up on this issue.

    Sunday, January 4, 2015 10:07 PM
  • Monday, January 5, 2015 3:03 AM
  • Thanks LemonStreet. I've already gone through the links above but still not able to find the source of crash. 

    The code is compiled with .Net 4.5.2 and is running on Windows Server 2008 R2 with .Net 4.5.2 installed. The KB article points to a bug in .Net 4.0 framework. Is this fixed in .Net 4.5.2 or am I seeing the bug causing the crash in our service?

    Thanks,

    Shweta

    Monday, January 5, 2015 6:26 PM