v71 at October 26th, 2012 19:15 — #1
Hi everybody , for 2 days i am banging my head trying to understand what is going on, visual studio bulding time increased so much that i cannot compile anymore , since it takes for ever, even messages in the output window which i normally use to log things out , take a long time to appear in the same window.
This happens after i run the program once or two times, i tried with the release only , debug mode, unloading symbols or whatever , it doesn't seems to change anything i disabled also the antivirus and there are no applications in the background that might be the potential causes.
This happened 2 days ago and i didn't change anything in project configurations.The strane things is that the computer , is still slwoed down , even if i close the same visual studio.
Do i need to uninstall visual studio 2010 and reinstall it again ?
has anyone eve experienced this tragedy ??
What is the best c++ enviroment for a mac ? i know about xcode, how does it performs against visual studio ??
i'd like to skip this M\\$ crap for ever
reedbeta at October 26th, 2012 20:39 — #2
Have you looked in the task manager to see if something is taking up a large amount of CPU time? Or a large amount of memory perhaps? Especially when the slowness continues after closing VS, there should be something identifiable.
thenut at October 26th, 2012 21:10 — #3
VS 2010 will open a project for the first time a little slowly because it will cache all the header files used by your sources, but overall compilation times should not suffer nor should the runtime debugger. Subsequent builds should be faster if you have the minimal compile flag set (under C++/Code Generation), which it is by default.
You might want to check your box to make sure all the hardware is running optimally. If after closing VS you're still having slowdowns, then it could be a hardware problem. Check your CPU and motherboard temps, check your RAM for memory faults and excess paging by the OS, check your HD fragmentation level and clean it up, and test your video card.
I'm not a big fan of XCode. I would personally use Eclipse over it simply because the UI in Eclipse is better. GDB is also better integrated into Eclipse compared to XCode.
i'd like to skip this M\\$ crap for ever
Some things MS does is undeniably bad, but Visual Studio is definitely not one of them. No IDE comes even close to productivity.
v71 at October 27th, 2012 04:30 — #4
Hardware doesn't have any problems, i am sure of it , i noticed that i get first chance exceptions and form then on , the pc slows down
the strange fact is that it started slowing down 3 days ago, i have always had those exceptions and the documentation says they are not
an indication of bad coding practice.I get them even if i start a fresh project and all the files are created by the visual studio.
I am thinking to switch to windows 7 and install visual studio 2012 express , since i don' tthink itd a trivial thing to fix.
jbadams at October 27th, 2012 05:08 — #5
It sounds like there's a problem with your computer, operating system, or visual studio installation. It's not normal for a freshly created Visual Studio project to throw exceptions, and it's not normal for there to be a slowdown that persists after Visual Studio has been closed.
Hardware doesn't have any problems, i am sure of it
Are you sure because you actually checked, or just because you don't believe the hardware is at fault? Something is wrong with your set-up, and hardware problems could be to blame; if you haven't already done so it would be worth while actually checking. You should also check for viruses or malware.
You mentioned switching to Windows 7 -- which version are you currently running?
fireside at October 27th, 2012 07:42 — #6
It sounds like a low memory issue. Maybe a leak in your program? Does Visual Studio run slow on another project after a fresh launch and boot?
v71 at October 27th, 2012 13:31 — #7
No its not a leak i use the visual leak detector, i think i found the reason, i disabled kaspersky and visual studio is no sluggish anymore, strange , because it never acted like that before, talking about first chance exceptions, i talked to the ms support and they keep saying its not a problem, strange.
The week of strangeness.......but i am still thinking about mac ......