The official source of product insight from the Visual Studio Engineering Team
If you're experiencing frequent “insufficient memory” errors when doing small cut or copy operations in Visual Studio 2010 RTM, please download this patch to see whether it resolves the issue.
Attempting to cut or copy small to moderate amounts of text in Visual Studio 2010 RTM may incorrectly cause the following error: "Insufficient available memory to meet the expected demands of an operation at this time, possibly due to virtual address space fragmentation. Please try again later."
There is a patch available for this issue in VS 2010 RTM.
Please note that both before and after hotfix installation, there are cases where Visual Studio accurately reports that not enough memory is available to complete a given operation. You may still see out of memory dialogs when attempting to make a very large cut or copy (50+ MB of data at once). However, the fix should ensure that Visual Studio is legitimately unable to find enough memory to execute such a large operation before displaying this dialog. The frequency of such a dialog should be dramatically decreased after installing the hotfix.
If you have any questions about this issue, please feel free to post in the comments below. If you’re experiencing problems with cut, copy, and paste that do not involve this “insufficient memory” dialog, or if you’re seeing “insufficient memory” dialogs in cases other than cut/copy/paste, the root cause is likely different. For issues like this, please file a Connect bug and we’ll investigate.
Brittany Behrens Program Manager, Visual Studio Editor Team
I’m Brittany, a Program Manager on the Visual Studio Editor team. Some of you may recognize me from Connect bugs or as the main voice of @VSEditor on Twitter, and I’m responsible for a variety of Editor features. I love hearing from customers, so please let me know what you think!
Hi Brittany, i wonder where can we get a list of all the fixes for VS? thank you. i'm afraid that i would miss some of them.
Hi Brittany, please add auto-update feature into Visual Studio (and other products especially Internet Explorer of course too), and nobody will have to afraid of missing one of these fixes :)
@ Daniel Steigerwald, I think that Windows Update and Microsoft Update are both the appropiate way to update or patch this kind of bugs. Actually, Microsoft has used Windows Update to patch Visual Studio in the past :)
So, in my case, I would ask when Microsoft will release this patch using Windows Update... or maybe in Service Pack 1 for VS2010?
Best regards from Peru!
Since this is a hotfix, i doubt it would be released via Win Update, maybe ones they have confirmed it fixes the problems.
I'll be sure to try this one out asap.
Thanks Brittany, really appreciate you guys releasing this as a hotfix rather than waiting for SP1.
That's fantastic, glad to hear that this issue has been resolved. Thanks for the patch!
is this going to be available into the critical windows updates of windows 7 or other, so that we automatically can get updated?
@Grammy: There isn't a single list of all hotfixes available for Visual Studio 2010. The best way to find out whether a given issue has been hotfixed is to search for it (which tends to turn up blog posts about fixes or discussion threads between people with similar problems) or file a Connect bug. If you file a Connect bug for something we've already fixed, the product team will let you know that; if we haven't yet fixed it, the product team will take a look and often investigate the issue.
@Daniel Steigerwald: I'm not aware of a plan to integrate an auto-update feature into Visual Studio, but it would solve the problem of not knowing when there are hotfixes available. I'll give this feedback to the VS servicing team, which is the group responsible for the infrastructure and release process for hotfixes.
@Jorge Morales, @Tim, and @johnny: Although products other than Windows very occasionally release hotfixes via Windows Update, it's the exception rather than the rule. This particular VS 2010 hotfix is unlikely to be included in Windows Update. However, we generally *do* include hotfixes for Visual Studio in any future VS service packs.
@Daniel Smith and @Nick K: No problem! Glad we could help :-).
Thanks for commenting!
I have installed this hotfix and found that C# editor performance and responsiveness has significantly dropped. Has anyone else had this experience?
Great! Thanks for this fix, this problem was incredibly annoying.
Now, if only you could fix the System Out of Memory errors I get on occasion when I build large projects, especially those that use WPF and XAML. :)
Keith I use to have that prb also especially when building My Silverlight solution that had 14 projects, after 2 or 3 builds I start getting that error and had to restarts vs.net, then I found this stevenharman.net/.../hacking-visual-studio-to-use-more-than-2gigabytes-of-memory.aspx
this refers to VS.net 2008, but I did the same for vs.net 2010 and work like a champ, since I did this never had that SystemOutofMemory exception and it fixed also my copy paste error.
just my 2 cents.
@Brad: That's odd; this hotfix is very targeted and modifies a code path that's only hit on cut/copy, not while typing or during general editor usage. Even when the new code path is hit, we're actually executing *less* code than before the hotfix. Would you mind giving a little more information?
- Which scenarios degraded? e.g. typing, scrolling, open file, start debugging, etc.
- Did performance and responsiveness return to pre-hotfix levels after restarting VS? It's possible that the very first time you use VS after installing any hotfix, you could see a slight performance decrease. Typically it's not a noticeable decrease, but it should only occur once. Subsequent VS sessions shouldn't have any slowdown.
- If restarting doesn't help, could you try uninstalling the patch to see whether that resolves the issue? If so, we'd like to investigate further.
I’m a little bit more convinced that there’s a problem of memory leakage at the source parser module. I got my crashed code back (1st comment) and started working with it again, but this time with the patch uninstalled. It seemed well until I sensed that VS was becoming very slow again. I checked memory consumption and it was 900 Mb to devenv.exe. Then, I closed my .aspx file and his code behind (I was with only this two files opened) and memory got free down to 500 Mb usage. After that, I tried to close VS and it showed an insufficient virtual memory error and asked for restart. Note that I have 4 GB Ram, and I double checked if it was really a lack of resources. It was not.
@Cristiano: This patch does not fix any potential memory leaks in VS 2010, nor does it address slowness or performance issues; it's very localized to cut/copy. Although they're probably not related to this hotfix, we'd definitely like to investigate the problems you're seeing. Could you file a Connect bug at connect.microsoft.com/visualstudio with as much information as you know? The bug will be routed to a VS product team for further investigation.
Could you help me to solve the issue when installing vs2010 on win7 error 1603
VC 9.0 Runtime(x86)Error 1935