4 ms·
Someday, I'd love to see an x64 Visual Studio. I've read the arguments (there's two canonical blog posts about it), but I'm just really sick of it hitting the
by douche 10y ago
Someday, I'd love to see an x64 Visual Studio. I've read the arguments (there's two canonical blog posts about it), but I'm just really sick of it hitting the memory limits on a 32-bit process all the time, when I have another 12 - 28 GB of RAM sitting unused.
- EpicEng 10y agoI'm curious; what are you working on exactly? I have worked on some rather large code bases in C++ and C# and have never seen VS eat that much memory.
- douche 10y agoFor some reason, it tends to choke and die if you have open C#, JS and html/cshtml files at the same time. Particularly if you have multiple monitors, and drag some editor windows onto the other desktops. Having the WinForms or WPF designers open also tends to bring things to a crawl. I do also run ReSharper, which does not help things. Routinely, I'll have open about 10-15 code files, that total up less than 1 MB, and Visual Studio will be chugging up 1.5 GB of memory, locking up for ten seconds when I go to type.
- EpicEng 10y agoInteresting. I don't do front end stuff or web development, so I've never hit that scenario. Lots of files open and whatnot, but never an issue. I also dumped Resharper a while back due to it generally slowing everything down.
- jackmott 10y agoVS 2015 update 3 has reduced the memory usage a lot, may help if you don't have it yet.