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.
Related
I decided to migrate to visual studio 2019 for my mfc c++ application from visual studio 2015.
I have installed all the required SDKs and chose target platform Windows 10, version 10.0.18362.0 and toolset visual studio 2019 (v142). Previously in visual studio 2015 I had Windows 8.1 and v140.
Everything compiles and I can debug the application, however I get strange behaviour for CSingleLock and CCriticalSection where static CCriticalSection objects are null or invalid causing null reference crashes. Static variables seem to have a mind of their own having random values in child frames. The application will open one child frame, but I cannot open multiple child frames simultaneously as the treecontrol in the main frame is misbehaving and will not change on click, the clicks are registered but the treecontrol is unable to get a handle to the ParentFrame (GetParentFrame) to open a new frame. Nothing untoward shows up in the output windows.
In visual studio 2019 I then changed toolset to v140 (Visual studio 2015) and all works as expected.
Has anyone got anything similar happen to them, is there anything I need to do different in code between the two toolsets or does anyone have any suggestions ?
I realise this post does not have much details as I am just fielding atm, if anyone needs more infro please let me know.
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.
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?
I recently updated my system from Windows 7 to Windows 10. Before I did this, my Visual Studio C++ compiler (2013) and debugger was working fine but when I ran the debugger, I would occasionally get the following message:
The Visual Studio 2015 Remote Debugger (MSVMON.EXE) does not appear to be running on the remove computer. This may be because a firewall is preventing communication to the remove computer. Please see Help for assistance on configuring remote debugging.
When I got the message, I would restart the debugger and the message would go away. After upgrading to Windows 10, every time I run the debugger, I get this message. Then the debugger does not run. So, I upgraded to Visual Studio C++ 2015 hoping it would fix the problem. It does not. I also use ZoneAlarm as my firewall. I thought that might be the problem. So I turned off ZoneAlarm but that did not help.
What am I doing wrong?
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: