Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
windbg - Failed to retrieve segments for gc heap RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, 

    I have a 32 bit managed windows service hosted on a 64 bit machine. 

    there is Outofmemory exception which i'm trying to analyse using windbg. 

    have loaded all the symbols(took those 3 sos, mscorwks and mscorordacwks_x86_x86_4.0.30319.1026.dll from server(renamed the dll as shown here)

    but everytie i try to get dump heap I get following error. can you please help me with this problem?

    Error requesting heap segment 0000000097dd0000
    Failed to retrieve segments for gc heap
    Unable to build snapshot of the garbage collector state

    memory dump was taken from default taskmgr. (i presume its 64bit)

    Kavya

    Peace, Kavya

    • Moved by Barry Wang Wednesday, December 16, 2015 9:59 AM
    Tuesday, December 15, 2015 4:57 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you. I found the solution as following:

    problem first: system is 64bit. process is 32bit. the memory dump i took from task mgr was 64bit. when i used 32bit windbg, i got above error. so I grabbed the memory dump from 32bit taskmgr and I can now navigate through the problem areas. 

    Although, i'm struggling to get the string out as I get 

    <String is invalid or too large to print>
    Is this something you can please help me with? how do I output the string?

    Peace, Kavya

    This is "where is" forum for help on where best to ask questions. You'll need to re-ask over here.

    https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=perfmon%2Cwindowsgeneraldevelopmentissues%2Cwindbg&filter=alltypes&sort=lastpostdesc

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Mike Laughlin Wednesday, December 16, 2015 2:52 PM
    • Marked as answer by Just Karl Monday, December 28, 2015 8:33 PM
    Wednesday, December 16, 2015 2:47 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Kavya_Shiva,

    This forum is about install/uninstall .NET Framework. So analyze dump file is not a supported scenario here. I recommend you create a support ticket to Microsoft to ask for help about analyze your dump file.

    By the way, I don't know which forum in MSDN is suitable for this issue. Maybe moving your case to "where is the forum for" will be more reasonable.

    By the way, here are some reference about how to analyze the dump:

    https://msdn.microsoft.com/en-us/library/windows/hardware/ff538058%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

    https://msdn.microsoft.com/en-us/library/windows/hardware/ff543991(v=vs.85).aspx

    Best regards,

    Barry

    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.

    Wednesday, December 16, 2015 9:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you. 

    I have got to a stage of looking at threads throwing OOM. but it is not giving much info because of failure to analyse gc state. will probably raise a ticket

    Peace, Kavya

    Wednesday, December 16, 2015 11:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You might try them over here.

    https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=perfmon%2Cwindowsgeneraldevelopmentissues%2Cwindbg&filter=alltypes&sort=lastpostdesc

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Mike Laughlin Wednesday, December 16, 2015 1:33 PM
    Wednesday, December 16, 2015 1:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you. I found the solution as following:

    problem first: system is 64bit. process is 32bit. the memory dump i took from task mgr was 64bit. when i used 32bit windbg, i got above error. so I grabbed the memory dump from 32bit taskmgr and I can now navigate through the problem areas. 

    Although, i'm struggling to get the string out as I get 

    <String is invalid or too large to print>
    Is this something you can please help me with? how do I output the string?

    Peace, Kavya

    Wednesday, December 16, 2015 2:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you. I found the solution as following:

    problem first: system is 64bit. process is 32bit. the memory dump i took from task mgr was 64bit. when i used 32bit windbg, i got above error. so I grabbed the memory dump from 32bit taskmgr and I can now navigate through the problem areas. 

    Although, i'm struggling to get the string out as I get 

    <String is invalid or too large to print>
    Is this something you can please help me with? how do I output the string?

    Peace, Kavya

    This is "where is" forum for help on where best to ask questions. You'll need to re-ask over here.

    https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=perfmon%2Cwindowsgeneraldevelopmentissues%2Cwindbg&filter=alltypes&sort=lastpostdesc

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Mike Laughlin Wednesday, December 16, 2015 2:52 PM
    • Marked as answer by Just Karl Monday, December 28, 2015 8:33 PM
    Wednesday, December 16, 2015 2:47 PM