How can we help you today? How can we help you today?

816 crashed VS2008 while trying to decompile an assembly

While decompiling an assembly, it froze at 5%, waited for a very long time, after which VS 2008 crashed.

To replicate, install the latest build of Resharper addon (I tried with EAP build 1573), and try to decompile JetBrains.Platform.ReSharper.VSIntegration.dll
yurik
0

Comments

8 comments

  • Alex D
    I happen to already be running that build of Resharper, I'll take a look.
    Alex D
    0
  • Alex D
    Ah, that's a known infinite recursion in reflector's engine causing a stack overflow. I may be able to fix it, but I can't promise.
    Alex D
    0
  • yurik
    Well, one may only hope :)
    I would like to continue testing reflector pro, but it says it will expire soon. Is there a way to postpone it?
    yurik
    0
  • Alex D
    The next build lets you get another 14 days.

    Cheers,
    Alex D
    0
  • cdonovan
    I'm having the same problem when decompiling Microsoft.Practices.EnterpriseLibrary.Logging.dll from version 4.1 of the Microsoft Patterns and Practices Enterprise Library. The decompile proceeds to 93% then stops and eventually Visual Studio 2008 crashes.
    cdonovan
    0
  • Clive Tong
    cdonovan wrote:
    I'm having the same problem when decompiling Microsoft.Practices.EnterpriseLibrary.Logging.dll from version 4.1 of the Microsoft Patterns and Practices Enterprise Library. The decompile proceeds to 93% then stops and eventually Visual Studio 2008 crashes.

    Thanks for the report. This was fixed in internal build 896.
    Clive Tong
    0
  • blindahl
    Another one - VS2010b2, decompiling Microsoft.VisualStudio.Editor.Implementation. Gets to 30% then crashes after a LONG wait - 15-20 minutes, maybe
    blindahl
    0
  • Clive Tong
    blindahl wrote:
    Another one - VS2010b2, decompiling Microsoft.VisualStudio.Editor.Implementation. Gets to 30% then crashes after a LONG wait - 15-20 minutes, maybe

    Thanks for the report. This was the same bug reported in the message above, which was fixed in internal build 896.
    Clive Tong
    0

Add comment

Please sign in to leave a comment.