tag:blogger.com,1999:blog-20032820.post3617543000143622153..comments2024-03-25T20:37:11.000+13:00Comments on Manni on DotNet: Visual Studio 2010, ReSharper 5 and Memory ConsumptionManfred Langehttp://www.blogger.com/profile/01100831606055102208noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-20032820.post-59459321369750905542011-07-26T05:10:29.445+12:002011-07-26T05:10:29.445+12:00The answer you are referring to is different to wh...The answer you are referring to is different to what I have described here. Regardless of whether ReSharper is implemented as a "package" it will consume broadly speaking memory for two purposes: a) for its binaries and b) for data once a solution has been loaded. I don't expect the memory for the binaries back. I want back the memory it needs while a solution is loaded. I expect that memory back once the solution has been closed. The observation I describe is with regards to then working on a project and opening/closing it. With memory fragmentation and being implemented (almost) exclusively in .NET I expect the graph for the memory consumption to reach a maximum at some point. Or at the very least the incremental memory consumption should become smaller (the differential becomes smaller). However, memory consumption increases linearly (differential stays the same) which suggests that ReSharper in the version I used for the test contains a memory leak.Manfred Langehttps://www.blogger.com/profile/01100831606055102208noreply@blogger.comtag:blogger.com,1999:blog-20032820.post-15037646026189337192011-07-22T01:46:56.171+12:002011-07-22T01:46:56.171+12:00See ( https://connect.microsoft.com/VisualStudio/f...See ( https://connect.microsoft.com/VisualStudio/feedback/details/526312/vs2010-very-high-memory-usage-very-slow : Posted by Microsoft on 19.04.2010 at 09:52 )<br />" if your expectation is that on closing the project you will get back all the memory used when the package that handles that project type loaded, you will be disappointed."Anonymousnoreply@blogger.com