I created a Visual Studio C++ project, write a game (about 10K-lines).
Yesterday, I compile and ran it in release mode, then I got some access violation error.
My program doesn't have any virus-like command, the closest one is just the array access,
so I think it came from array-index-out-of-bound.
Therefore, I aborted my program - using STOP button - and edit my code, test it again - F5 (release mode, not-optimized).
This happened around 10-20 times - crash & debug ; my happy life cycle.
When I shut down, Windows 7 created a popup error about access violation.
(It has sometimes happened before, but has never caused any serious long-term affect.)
Problem
Today, after I turned on the computer, it began to act strangely
Windows and Visual Studio start up a little slower. (I may be biased.)
Windows task bar (that has the start button) is quite non-responsive. (obvious, happen only once)
Visual Studio : some shortcuts (Ctrl K + Ctrl O to switch .cpp /.h) not work anymore except it open a file instead (look like it recognize only Ctrl O).
Visual Studio : I can't assign any shortcut that has 2 Ctrl button (e.g. Ctrl xxx + Ctrl xxx)
I test with on-screen keyboard, after a bit of testing, my computer crashed. (mouse cursor disappear)
After I turned on my computer again - avoid opening Visual Studio, my computer act as almost normal, but alt+tab not work anymore.
Note that I didn't install any new software in the last 7 days.
Question
Is it possible that bug / crash of my C++ program (always run within Visual Studio) can destroy some structure of Visual Studio or OS unintentionally?
If so, is there any setting of Windows / Visual Studio to prevent it?
Related
Sometimes if i Debug a C++ program in Visual Studio 2015 it freezes my whole PC so i have to restart it. Windows doesn't respond to anything even not to commands like CRL+ALT+DEL. Even other programms i have open dont respond anymore and everything freezes.
When this happens Visual Studio is loading a DLL as seen in the bottom left corner and then everything just freezes and only the Windows loading cursor still spins.
Fixed it myself: i clicked on Tools->Options->Debugging->Symbols and disabled Microsoft Symbol Servers everything works fine now.
In our company me and some of my colleagues switched from windows 7 do windows 10. All of us noticed the same bug in the Visual Studio 2013:
When the debugger hits the breakpoint and stay there, writing a text starts annoyingly lag anywhere (e.g. in visual studio, notepad, browser...). Everything else on PC works without lagging.
I also have noticed that it happens only if we debug the application which extensively use the GPU.
P.S. Yes we have an updated drivers for Nvidia.
Im currently running Visual Studio 2013 with Update 3.
My project is an Arduino project with the Aruduino IDE for Visual Studio.
When I start typing Intellisense is showing up and giving suggestions, but without Pre-Selection like
in a normal C#, C++, Java... project.
I've already tried CTRL + ALT + SPACE to switch to Completion mode but unfortunately didn't solved the problem (Nothing happens).
If I hit CTRL + SPACE with active suggestion window, auto-completion works quite fine as long as the current window is still open.
Also if I change the Member List Commit Aggressive in
Tools -> Options -> Text Editor -> C++ -> Advanced
from False to True, it doesn't even show suggestions but if I hit CTRL + J after I typed something, autocompletion works fine but again only in the current window.
Hope you can Help
I am using Visual Studio Premium 2013 Update 2 on a freshly installed (fast) machine with Windows 8.1 Update. Everything is running smoothly, only one thing bugs me:
Problem
When I debug a native C++ project (debug build) by going from line to line with F10 ("step over") it takes 1-2 seconds to go to the next line when I press the F10 key.
What I tried
I looked at several other questions related to slow debugging and made sure that neither of the following is not the reason in my case:
Everything is local (app and all data), no network shares involved
Disabling the Microsoft symbol server did not help
I only have a single breakpoint
Using the menu/toolbar instead of the keyboard does not make any difference
In the default configuration "edit and continue" is enabled, but apparently not for native code:
When I disabled "edit and continue" completely, F10 stepping became much faster (0.5-1 s). The speed is tolerable now. I had to restart Visual Studio after I changed the configuration to this:
I have written a program in vc++ that has different behavior in various case as below.
When I run it by F5 it works properly in release mode.
When I run it by ctrl + F5 it crashes when I start to send data to the program.
Outside of visual studio it crashes immediately.
I don't know how to find the bug. Any idea on
what is different between these cases?
Running ctrl + F5 will run the application without debugger.
(http://msdn.microsoft.com/en-US/library/8b59xk0f(v=vs.90).aspx)
This is not the same as running in release mode.
You can run your application in debug mode but without debugger.
It sounds stupid but is for example helpful if you want to stop the console from closing on exit. (How to stop console from closing on exit?)
You need to understand the difference between running an application in debug mode and release mode. F5 will generally help you to debug the application and ctrl + F5 will execute the application. There might be some issues in release mode that makes your vs to crash. Read this to get an understanding.