Memory Leak in Devenv.exe
I'm using resharper 2.5 RTM build and I need some advice on memory consumption by the IDE while editing .aspx files.
I have been building more asp.net stuff, and when editing html, the memory consumption of devenv.exe goes through the roof. Today I made an aspx page from scratch, inherits a master page & a page base class. At about 826 lines of html code, resharper started dying & delaying my typing, I look and I see that memory consumption is right about 900mb for devenev.exe.
I tried unloading resharper via add-ins menu, which restored my ability to type without delay's, but the devenv.exe memory consumption is still at about 891mb. I have only the one file open, and its in a solution with about 8 projects. Adding lines to that open aspx file contributes directly to memory consumption by devenev.exe
Is this something visual studio is having a hard time with, or is it resharper? Does resharper unload from devenv.exe when i take it out of active add-ins?
Does anybody know any settings that can ease up the memory pressure in visual studio or resharper?
Attachment(s):
2007-01-03_163529.png
Please sign in to leave a comment.
Hello Wil,
I think that the best thing to try is to work for some time with ReSharper
disabled so
that VS doesn't load it on startup. Will the memory usage continue to grow
even without ReSharper?
Concerning your question about unloading ReSharper - the fact that you unload
it via the Add-In Manager
definitely doesn't mean that all the memory ReSharper consumed will be immediately
reclaimed to the system.
This may happen at some point in the future in this session or VS, or even
may not happen at all - it's
up to the .NET garbage collector to decide whether to reclaim the memory
to the OS or just reserve it for future
allocations.
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello Dmitry,
we are using Resharper 2.5 and VS 2005 SP1.
We have exactly the same effect as described by Wil.
By the same token we also faced problems regarding to non-responding keystrokes because of the high memory consumption (ReSharper consumed up to 900MB).
After uninstalling ReSharper the memory consumption returned back to normal.
Best regards,
Paul.
Just to second - I am experiencing quite massive memory leaking in ReSharper 2.5.1 too. If for instance i rename a control using the designer, Resharper will look for references etc., and if I repeat this - say ten times or so - 60M memory has been consumed. The trend continues until I have to restart VS2005.
Hello mrmajestyk,
are you sure that it is ReSharper that looks for references after changing
control's name in the designer? I remember
that VS 2005 is doing that itself...
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
That may well be in fact. But the thing is that the memory consumption grows seemingly wo. bound when ReSharper is loade, but wo. ReSharper there is no problem. I was thinking of the rename refactoring as the culprit because I've used it a lot and doing that seems to be the fastest way to run out of memory. But you're right - it is VS2005 that does the looking. ReSharper just seems to be doing the leaking :(
I know that I'm jumping in here late, but I think Resharper's background
indexing is a "heavy user" -- to quote the movie "Super Size Me". All I've
done is load Resharper with the memory usage showing and, as I open each
file, the memory goes up and up and up. After I close each file, the memory
stays where it is.
During normal usage, the Resharper features I use without even thinking are
the "Go to Definition" shortcut and the "Find Usages" shortcut. In a large
solution, this has me hopping from one file to another, barely aware of the
fact that I have opened upwards of 16 files. This eats up memory fast, and
it is a little disheartening to know that the best way to get it back is
to restart VS2005.
But we really should not be that miserly with "free memory". I want it all
used, as "free memory" is "unused memory" which might as well be "wasted
memory". What really irks me are the slow downs where one cannot type while
VS.NET/Resharper is busy processing who-knows-what in the background. Indexing?
I wrote a simple little ReSharper plugin that just forces Garbage
Collection. It helps to "fight back", but memory usage keeps going up over
time. So eventually I have to restart VS, but atleast not as often.
---
Richard
"flipdoubt" <flipdoubt@nospam.com> wrote in message
news:da27a8e44f3718c918a62a6c7dba@news.jetbrains.com...
>I know that I'm jumping in here late, but I think Resharper's background
>indexing is a "heavy user" -- to quote the movie "Super Size Me". All I've
>done is load Resharper with the memory usage showing and, as I open each
>file, the memory goes up and up and up. After I close each file, the memory
>stays where it is.
>
>
I used to have the same problem w/ the IDE seemingly leaking memory on my laptop, where at time it would consume 1GB+ of RAM. However, I recently discovered that if I disable the company-installed combo firewall/virus/malware/spyware checker, the problem goes away.
My setup is Visual Studio 2005 (mainly web application projects) + ReSharper (the only add-in) + ClearCase + aforementioned company software. My theory is that the leak has to do w/ ReSharper frequently reading from and writing to its disk-based cache. And each of these actions was triggering some sort of check by the aforementioned program, resulting in a leak.
Since I only use the laptop in trusted networks (either at work or at home), I am now developing happily w/ ReSharper and Visual Studio 2005 now, minus the annoying memory leak. But, YMMV...
It's simpler than that Dmitry. I have a rather sizeable ( for me ) solution
with about close to 100 files in it. If I open a file, it goes up by about
3-9 Mb ( depending on how big the source file was, and obviously how complex
the class is ). If I close it immediately, I MIGHT get 500K back, might. But
it never goes down.
Initially loaded, with my solution, it's using 85.7 Mb, the minute I open
one screen ( i.e a form with say, a tab control, 6 pages, and about 10
controls on each page....fairly busy form ). The memory consumption goes up
to 106Mb. If I close that designer, it does NOT go down. Ever. You could go
have a cup of coffee, lunch with your wife, it doesn't matter. It won't go
down. I literally took my system from a working set of 400Mb to over a
Gigabyte once I'd opened maybe 5 screens similar to the first one. It did
this on the RTM and it does it in later releases.
And actually, I think later builds than RTM seem to use up more. I know,
weird.
Marcelo
"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d0ed48c912d5c9c41feb@news.intellij.net...
>
>
>
>
>
>
>> Just to second - I am experiencing quite massive memory leaking in
>> ReSharper 2.5.1 too. If for instance i rename a control using the
>> designer, Resharper will look for references etc., and if I repeat
>> this - say ten times or so - 60M memory has been consumed. The trend
>> continues until I have to restart VS2005.
>>
>
Hello Marcelo,
so does the memory get reclaimed with ReShaper disabled? I mean, if you disable
ReShaper and repeat experiment with opening large files,
do you observe the memory returning to the system (I suppose you're using
a tool like Task Manager for tracking this)?
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Hello mrmajestyk,
>>
>> are you sure that it is ReSharper that looks for references after
>> changing
>> control's name in the designer? I remember
>> that VS 2005 is doing that itself...
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Just to second - I am experiencing quite massive memory leaking in
>>> ReSharper 2.5.1 too. If for instance i rename a control using the
>>> designer, Resharper will look for references etc., and if I repeat
>>> this - say ten times or so - 60M memory has been consumed. The trend
>>> continues until I have to restart VS2005.
>>>
Dmitry,
Yes, this is partially how I was looking at memory usage ( I also happen to
know a fair bit about how the memory manager in Win32 itself works. I'm an
old programmer, what can I say. ).
One curious note: When you load VS2005, if you go into the Add-in Manager
and disable the R# plugin ( even if you disable the Load at Startup ), it
completely ignores the setting, and loads it anyway.
What I then did was to disable it, exit and restart VS2005. Then as soon as
the menu became available for Tools, I went back into the Add-In Manager and
disabled the plugin again as VS2005 was finishing to load.
I ended up with the base 85-95Mb I would've expected. The difference is that
once I loaded the Solution, it maybe went up 5Mb, and once I opened and
closed the same form as before, the memory went up by about 25Mb ( amazing a
form like that would occupy that much memory ). Closing and re-opening the
same form didn't make the memory jump up as before, and actually after a few
times of opening and closing, the memory dropped down by 5Mb or so.
Yes, all these measurements were by "eye-balling", but I've been eyeballing
working sets of operating systems for over a decade and a half ( that's what
happens when you have to make a whole OS with UI run in a working set of 2Mb
of RAM, maybe you've heard of it, IBM OS/2 v1.3 ? )
Interestingly enough, as I was typing the first part of this reply,
devenv.exe was in the background. ( that lasted about 5 minutes ). Taking a
look at it again, without the form loaded, the WS went dow to 18Mb. Once I
opened the form back up, it went up to 52Mb ( good, so there's a little more
confirmation that the form takes about ~32-34Mb to load and keep in
memory ).
Letting it sit there for a few minutes, the WS settled around 54Mb. I then
went into the tools->Add-In Manager-> R#, and activated it.
The WS grew to a whopping 186Mb ( And I have NO forms open. Nothing. ). I'm
sitting here watching it idled and amazed at what could possibly require
132Mb.
My next text will be to create a small solution and follow the same steps,
and see what the outcome is.
I will report back my results.
Marcelo
"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d0fb88c91e2960025b13@news.intellij.net...
>
>
>
>
>
>
>> It's simpler than that Dmitry. I have a rather sizeable ( for me )
>> solution with about close to 100 files in it. If I open a file, it
>> goes up by about 3-9 Mb ( depending on how big the source file was,
>> and obviously how complex the class is ). If I close it immediately, I
>> MIGHT get 500K back, might. But it never goes down.
>>
>> Initially loaded, with my solution, it's using 85.7 Mb, the minute I
>> open one screen ( i.e a form with say, a tab control, 6 pages, and
>> about 10 controls on each page....fairly busy form ). The memory
>> consumption goes up to 106Mb. If I close that designer, it does NOT go
>> down. Ever. You could go have a cup of coffee, lunch with your wife,
>> it doesn't matter. It won't go down. I literally took my system from a
>> working set of 400Mb to over a Gigabyte once I'd opened maybe 5
>> screens similar to the first one. It did this on the RTM and it does
>> it in later releases.
>>
>> And actually, I think later builds than RTM seem to use up more. I
>> know, weird.
>>
>> Marcelo
>>
>> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
>> news:c8a8945d0ed48c912d5c9c41feb@news.intellij.net...
>>
>>> Hello mrmajestyk,
>>>
>>> are you sure that it is ReSharper that looks for references after
>>> changing
>>> control's name in the designer? I remember
>>> that VS 2005 is doing that itself...
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> Just to second - I am experiencing quite massive memory leaking in
>>>> ReSharper 2.5.1 too. If for instance i rename a control using the
>>>> designer, Resharper will look for references etc., and if I repeat
>>>> this - say ten times or so - 60M memory has been consumed. The trend
>>>> continues until I have to restart VS2005.
>>>>
>
>
Dmitry,
Following the suggestion of another POST, I disabled the auto-startup of R#
via the registry.
Startup - 37Mb
Load Solution - 73Mb
Open ONE form ( large, as described before ) - 109Mb
Close form - 108Mb
Allowed Idle - 7.6Mb !!!!!! ( 3 minutes ) Open same form as before - 54.7Mb Allowed Idle - 10.2 Mb !!! ( 2 minutes ) < Minimized > Restored VS window - 15.5Mb Clicked on Form - 54Mb Closed Solution - 58Mb Minimized - 6Mb Restored - 9.4Mb Activated R# ( Tools->Add In Mgr->etc.etc ) - 66.1Mb ( Note that no solution is loaded ) Loaded same solution once more - 128.5Mb ( sitting idle, no forms loaded ) Minimized - 7.5Mb Restored - 21.7Mb Opened Form - 71.5Mb Clicked on Form - 72.2Mb Built Solution - ( up to 128Mb, down to 99.6Mb ) Rebuild Solution - ( up to 181Mb, down to 148.9Mb ) Rebuild Solution - ( up to 192Mb, down to 156.3Mb ) Switch from Debug to Release Configuration ( up to 209Mb, down to 205Mb ) Build Solution - ( up to 248.5Mb, down to 217.8Mb ) Minimize - 15Mb Restore - 23.2Mb After running through this I'm wondering if VS may have an issue here and R# may only be peripherally involved. I encourage anyone else who's experienced this to recreate the same steps with the Task Manager up and running, noting the memory usage at each stage. Very strange....very strange indeed. Marcelo "Dmitry Shaporenkov" ]]> wrote in message
news:c8a8945d0fb88c91e2960025b13@news.intellij.net...
>
>
>
>
>
>
>> It's simpler than that Dmitry. I have a rather sizeable ( for me )
>> solution with about close to 100 files in it. If I open a file, it
>> goes up by about 3-9 Mb ( depending on how big the source file was,
>> and obviously how complex the class is ). If I close it immediately, I
>> MIGHT get 500K back, might. But it never goes down.
>>
>> Initially loaded, with my solution, it's using 85.7 Mb, the minute I
>> open one screen ( i.e a form with say, a tab control, 6 pages, and
>> about 10 controls on each page....fairly busy form ). The memory
>> consumption goes up to 106Mb. If I close that designer, it does NOT go
>> down. Ever. You could go have a cup of coffee, lunch with your wife,
>> it doesn't matter. It won't go down. I literally took my system from a
>> working set of 400Mb to over a Gigabyte once I'd opened maybe 5
>> screens similar to the first one. It did this on the RTM and it does
>> it in later releases.
>>
>> And actually, I think later builds than RTM seem to use up more. I
>> know, weird.
>>
>> Marcelo
>>
>> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
>> news:c8a8945d0ed48c912d5c9c41feb@news.intellij.net...
>>
>>> Hello mrmajestyk,
>>>
>>> are you sure that it is ReSharper that looks for references after
>>> changing
>>> control's name in the designer? I remember
>>> that VS 2005 is doing that itself...
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> Just to second - I am experiencing quite massive memory leaking in
>>>> ReSharper 2.5.1 too. If for instance i rename a control using the
>>>> designer, Resharper will look for references etc., and if I repeat
>>>> this - say ten times or so - 60M memory has been consumed. The trend
>>>> continues until I have to restart VS2005.
>>>>
>
"Marcelo Lopez" <marcelol240@yahoo.com> writes:
Hi, sorry for jumping in on this discussion here. I just wanted to point
out (even if I'm quite sure that you know that) that Taskmanager only
shows the Working Set of the process, which is a completely different
matter than the really needed virtual memory.
Best regards,
Martin
Hello Martin,
one can customize the set of columns displayed in the Task Manager (VM Size,
Working Set and so on).
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> After running through this I'm wondering if VS may have an issue here
>> and R# may only be peripherally involved. I encourage anyone else
>> who's experienced this to recreate the same steps with the Task
>> Manager up and running, noting the memory usage at each stage.
>>
>
>
>
Just a note on the Minimize/Restore bit: I take it you are looking at the
"Mem Usage" column. If you add the "VM Size" column, you will note that,
while the physical memory shrinks when you minimize the app, the virtual
memory remains constant through the Minimize/Restore process. This is the
case for all WinForms apps.
Dmitry Shaporenkov <dsha@jetbrains.com> writes:
>
Of course, but the line indicating that after minimizing Viual Studio
the memory usage dropped to 6MB indicated to me that it was the Working
Set being displayed, as a working set trimming occures here by
default. But I might have misread the provided statistics.
Best regards,
Martin
There can be no doubt, though, that there is a leak. A big one.
Last night I was working on an ASP.NET project and had six files open when
I closed the lid on my laptop for the night. I don't remember what Resharper's
memory counter said last night, but right now it reads "Memory Usage: 235.4
Mb". In Task Manager, the devenv.exe process has a Mem Usage of 247,944 K
and a VM Size of 524,264 K.
Ouch. I guess it is best to close VisualStudio before hibernating your laptop.
I wonder if there is any commonality between the projects that see such explosive
memory consumption. Are they mostly ASP.NET projects? Do they use typed-datasets
or other generated code?
If so, I wonder if it would help were we given the ability to turn off code
analysis on certain chunks of code. If it is all the VS.NET generated stuff
in designer pages and typed-dataset pages adding to the problem, I could
do without code analysis on that code.
Mine are all asp.net projects. I use custom data type collections for data binding (generated transfer objects). But really it doesn't get that far. I can build the aspx form & run up to 900 megs of memory just building a simple webform... before i even get to the codebehind portion.
Thanks...Just realized that, I didn't have those extra columns ( bonk my own
head against the desk ) in Task Manager.
Sure enough, the VM size is pretty much the same.....so without a doubt,
there is definitely a memory leak ( or something is holding memory
unnecessarily ).
I hate having to turn off Resharper, but sometimes it simply makes VS2005
unusable.
Marcelo
"flipdoubt" <flipdoubt@nospam.com> wrote in message
news:da27a8e44fb138c91ef437a59a9e@news.jetbrains.com...
>> Minimized - 6Mb
>> Restored - 9.4Mb
>> Activated R# ( Tools->Add In Mgr->etc.etc ) - 66.1Mb ( Note that no
>> solution
>> is loaded )
>>
>> Minimized - 7.5Mb
>> Restored - 21.7Mb
>>
>> Minimize - 15Mb
>> Restore - 23.2Mb
>>
>
>
I have this problem with VS2005 and Resharper 2.5 (build 351, but I also had this problem with 326 and several builds in-between).
The solution I most often work in has about 20 dll projects, 5 console apps, 2 windows apps, and one website.
If I'm working in anything other than the website, no problem.
If I'm working in the website I see this problem at least once or twice per day.
If I uninstall Resharper, I don't see the problem at all.
Symptoms:
The memory use displayed in the VS taskbar climbs. It starts out at around 80 Mb, climbs slowly to over 300.
Response to my typing, clicking, or anything at all in VS slows dramatically.
At this point, I have two choices.
1 - try to save my work, close VS, and restart. Simply saving the work and closing VS at this point can literally take 10 minutes.
2 - if I don't close VS and reopen it as soon as I notice the drastic slowdown in performance, a resharper 'out of memory' error pops up. When that error pops up, there's no hope of saving work or even submitting the error, as the entire GUI is completely locked up and has to be closed through task manager.
Over the past 3 months or so I've uninstalled Resharper several times because of this problem. Each time I've gone a week or so with no problems at all, then reinstalled Resharper when a new 'stable' or 'EAP' build is available, only to have the same problem return.
.
Ditto for me. I love resharper but everyone else around me is starting to drop it because of these memory and performance issues.
Regards
Ian
Ian Cox wrote:
This is true for out team too. I like R# too much, but the memory leaks
of R# is terrible a others team mates leave R# :-((
--
Peter Sulek
terrorix@centrum.sk
Well....seems no one's interested in pursuing this. I have one screen where
there are 200+ controls ( controls for displaying sensor states, a/d
readings ), and it's a royal pain to work with if R# is up. Has someone
opened a Jira issue for this, or is 3.0 supposed to address this issue ?
Marcelo
"Marcelo Lopez" <marcelol240@yahoo.com> wrote in message
news:etejeb$mnm$1@is.intellij.net...
>
>
>
>
>>> Minimized - 6Mb
>>> Restored - 9.4Mb
>>> Activated R# ( Tools->Add In Mgr->etc.etc ) - 66.1Mb ( Note that no
>>> solution
>>> is loaded )
>>>
>>> Minimized - 7.5Mb
>>> Restored - 21.7Mb
>>>
>>> Minimize - 15Mb
>>> Restore - 23.2Mb
>>>
>>
>> Just a note on the Minimize/Restore bit: I take it you are looking at the
>> "Mem Usage" column. If you add the "VM Size" column, you will note that,
>> while the physical memory shrinks when you minimize the app, the virtual
>> memory remains constant through the Minimize/Restore process. This is the
>> case for all WinForms apps.
>>
>>
>
It's a shame that I have to concur. If you're working on a bunch of small
projects, with screens that have minimal visual interaction, everythings
fine. When you start dealing with complex displays that can show literally
hundreds of controls ( as in my case ), R# because practically unusable. I
have a 1GB of RAM, and I never have these problems when I'm running Eclipse
( I know I'm not supposed to say the "E" word on a JetBrains forum, sorry )
and use any of their visual editors. Only with Vs2005 and R#.
Marcelo
"Peter Sulek" <terrorix@centrum.sk> wrote in message
news:etvu2a$31b$1@is.intellij.net...
>
>> Ditto for me. I love resharper but everyone else around me is
>> starting to drop it because of these memory and performance issues.
>>
>> Regards
>> Ian
>
>