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

Out of Memory exception when decompiling.

I have a couple assemblies, which are pretty big. For example, one contains around 13.000 methods. When I select one in the decompilation dialog, it decompiles fine, but the memory usage of devenv.exe grows to around 500 MB. If I select several of those, I get an out of memory exception.

Furthermore, after decompiling them, the memory doesn't get freed anymore, so devenv.exe stays for instance at around 500MB. When I close Visual Studio and reopen it and start debugging, the memory doesn't grow that much anymore, so I'm guessing whatever (wonderful btw) you do, to decompile the assemblies, doesn't unload in the end.

Would be wonderful if you could fix that.

PS: I'm using Reflector Pro Beta build 892
bjoern.busch
0

Comments

4 comments

Sort by
  • Alex D
    I'll take a look. I know that we need to use some memory to provide the "Go To Definition" feature, but this should be relatively small, and should be loaded back in when you restart visual studio. So your issue sounds like it's more than just that problem.

    Thanks,
    Alex D
    0
  • Alex D
    I've found that this is caused by large object heap fragmentation, which I thought I'd eliminated a while ago, but obviously hadn't.

    I've fixed it now I believe, and the next release will have the fix.

    Thanks for pointing it out,
    Alex D
    0
  • bjoern.busch
    Glad I could help :)
    bjoern.busch
    0
  • bjoern.busch
    Just as a confirmation, in Build 918 it's working perfect. Thanks for the quick fix!
    bjoern.busch
    0

Add comment

Please sign in to leave a comment.