I've been (well, my whole team) experiencing extreme cases of memory leakage when developing in VS2005.
I opened a case with Microsoft Support and sent them some memory dumps from my development machine.
They just called back and pointed to Sourcegear Vault as showing a lot of consumption.
Are there any known memory leaks as of 3.1.2? Are they fixed in 3.1.7?
Memory Leak in Vault Source Control Plugin in VS2005 RTM?
Moderator: SourceGear
Vault is a C# app, and uses C#'s garbage collector to reclaim memory. This isn't to say we don't have a memory leak, but Vault does tend to use more RAM than a C++ app would, simply because of the technology it uses.
In answer to your question, no we are not aware of any major problems with memory leaks, but to be honest, it isn't an area that gets a lot of attention. Can you quantify what you are seeing, and which operations tend to consume the memory? Can you send us an example solution or project that would help us track it down?
In answer to your question, no we are not aware of any major problems with memory leaks, but to be honest, it isn't an area that gets a lot of attention. Can you quantify what you are seeing, and which operations tend to consume the memory? Can you send us an example solution or project that would help us track it down?
More info
Once our solution is loaded (mix of 95%vb 5%c#) and I start working, memory consumption creeps up continuously until all system memory is consumed and VS2005 crashes. While getting the dumps for MS yesterday, I saw devenv.exe consume an additional 1GB of memory between project load and IDE crash. By the time the crash dump was created, the devenv.exe footprint was over 1.5GB
Generally, the tasks I see this happen under are generally compilation and most disturbingly, just plain editing of source. I literally typed a single line of code and watched memory jump by 20MB. I deleted the line, and saw the memory go UP, not down.
I realize I'm playing mediator here, between the MS support engineers and you, and can only relay what they say they see in the Dump. I don't know if it's objects created by you, or by MS when loading your plugins. It'd be great to get your engineers on the line with my support guy and the MS enginners so you can talk debug stuff.
Our solution is 65 projects and thousands of files. It might be tough to get it to you, along with all the setup info. Besides I'm not sure if that would even fly as it is very proprietary in nature. But I can ask.
Generally, the tasks I see this happen under are generally compilation and most disturbingly, just plain editing of source. I literally typed a single line of code and watched memory jump by 20MB. I deleted the line, and saw the memory go UP, not down.
I realize I'm playing mediator here, between the MS support engineers and you, and can only relay what they say they see in the Dump. I don't know if it's objects created by you, or by MS when loading your plugins. It'd be great to get your engineers on the line with my support guy and the MS enginners so you can talk debug stuff.
Our solution is 65 projects and thousands of files. It might be tough to get it to you, along with all the setup info. Besides I'm not sure if that would even fly as it is very proprietary in nature. But I can ask.
gold support
BTW - i just discovered we have gold support with you. I didn't know that (the Keeper of the Licenses is not in today) when I opened the thread. Should this be moved to the Gold forum?
We'd be happy to connect with you and MS on this, just email me using the button below.
However, editing and compiling don't have anything to do with Vault, so one thing to figure out is whether the MS folks complained about Vault's RAM continually increasing, or just whether it is larger than they want it to be
I know we had to increase everyone's RAM in house here when we started dealing with VS 2005 because it consumes so much. In any case, give me an email and we can set things up.
However, editing and compiling don't have anything to do with Vault, so one thing to figure out is whether the MS folks complained about Vault's RAM continually increasing, or just whether it is larger than they want it to be
I know we had to increase everyone's RAM in house here when we started dealing with VS 2005 because it consumes so much. In any case, give me an email and we can set things up.