I have changed the name of something and now it froze, probably won't work until I kill Visual Studio (devenv.exe) again. Now the first time the thing hung and crashed itself, using resource monitor to resume first it was suspended and now i unsuspended it and it now said process not responding, so I had no choice but to wait and I killed it because it just wasn't responding. It wasn't hung waiting for an extension or resource to clear it just hung suddenly. The first time it froze happened when I try to change a code because I got too many errors, luckily, I have everything saved but now I'm scared I'm gonna lose my work. I need help fixing my visual studio issue, but now I can't code if the thing just sits and freezes. This is the second time. Help me, I don't want to have to lose my work.
Well, Visual Studio never crashes on me, I am on Windows 11 and I run the latest version of Visual Studio. All I was trying to do was change code because of constant errors. This is ridiculous, even more ridiculous if nobody wants to or willingly helps me
Related
I get this 'Visual Studio is busy' message often when I try to do anything in it. This happens in different situations. It can happen when VS starts before loading any solution. It can happen after loading a solution. I just upgraded today to 17.3.6 and it happened again. I have already reinstalled VS. I did a repair. I did a 'devenv /resetsettings', 'devenv /resetuserdata'. 'devenv /setup'. Deleted %USERPROFILE%\AppData\Local\Microsoft\VisualStudio\ \ComponentModelCache.
I did devenv.exe /log <path> and I didn't see anything glaring in the log.
I have a handful of extensions but haven't gone through disabling them and using VS without them. I need them for my work.
Once I get this message, there's nothing I can do but kill the process because VS never recovers from it. I am not seeing any pattern as to what might cause the issue and it seems it's random. I just have to keep killing and relaunching VS until I get a good instance (1-5 times).
Because it's random, I can't determine if anything I did from the above steps helps because VS can launch just fine sometimes.
I also recently changed the setting to not participate in the VS experience improvement program so that PerfWatson2 doesn't launch.
Any ideas on how to find the cause of this issue?
Just suddenly over the past day I'm having an issue with Visual Studio 2015 where it takes an age to start debugging anything. Even a simple console application with one line will take over 3 minutes just to start. Running without debugging is normal.
Things I've tried:
Enable Just My Code checked under General Debugging options
Created local cache of Symbols
Removed all Breakpoints
Deleted all user temp files
Reinstalled Visual Sudio
Nothing has had any effect. When starting debugging it just hangs and VS becomes unresponsive for a couple of minutes until it then will start debugging. Once running it is fine. I don't understand why this has suddenly just started happening.
My company have recently pushed McAfee out to all machines, but this has been running on mine for a while now without any issue so not sure why it would suddenly be causing this now. Has anyone else experienced this and if so how did you fix it?
I have disabled Just my code and disabled also diagnostic tools during debug in Tools->settings->debug
For the past couple of days, Visual Studio 2012 and 2013 have been hanging during debug mode. Most of the time, i dont get this issue until further into my project. When i press the Start Button, everything continues as normal, but then hangs with this message at the bottom of visual Studio statusBar.
Inside Task Manager, when i try to force taskkill, or end process/process tree, this continues to stay present in my running processes.
Even after a reinstall, nothing seems to help it. I did see somewhere on the Microsoft Developer forums where a person was told it was something to do with the windows sybmol server?. What do i need to do to fix this issue i am having?
After this occurs once, i am forced to reboot my computer. Even if i open Visual Studio after this happens, it still has the same issue.
Yesterday I wanted to continue working on a project of mine, so I started Visual Studio and asked it to run the project to remind myself, what was already implemented and what wasn't.
The project got built and started, but seemed to quit right away. No error message, nothing.
No matter what I did, whether I rebuilt the project or cleaned it, nothing changed.
This didn't make sense, since the last time I tested the project, it worked perfectly (and I didn't modify anything in the code since then)
So, I assumed I had a hidden bug somewhere in the code, that just didn't show up previously.
I put a Breakpoint somewhere near the beginning of the code, and ran the project.
As expected, Visual Studio paused the execution at the Breakpoint and highlighted it.
I decided to set another Breakpoint somewhere later in the code and continue execution, but before I could even move my mouse, the project stopped.
Restarting Visual Studio didn't help, but restarting the PC did. Therefore, I'm assuming that something on my system was terminating my project, shortly after execution begun.
Now my question is: What exactly happened, and especially: why did it happen?
The problem came back while I was writing this question. I don't feel like restarting my PC every couple of hours...
I really appreciate the time you took reading this and I look forward to your answers.
I'm aware that I'm answering my own question, but since I've solved it myself, I thought others might want to know how I did it (for the sake of future generations)
The thing is: I've recently added Visual C++ to Visual C# before Visual C# started having problems.
So I deduced, that maybe the installer for Visual Studio messed up with something and decided to reinstall Visual Studio.
Problem solved.
So: if your projects stop without warning even while paused on a Breakpoint and you've changed something in your Visual Studio installation (like added Visual C++ in my case), you might need to reinstall the whole thing.
Luckily, the Visual Studio installer offers a "Reinstall" option, so you don't need to uninstall and reinstall manually.
I found about this solution, after talking to a more experienced colleague. I just wish I asked him first. Still appreciate your efforts in the matter, though.
EDIT:
I recently noticed a similar bug acting up for C++ programs this time, where the window border would be outlined in red. The thing is: it's not Visual Studio's fault, but in fact Avast Antivirus' fault. More specifically, its Sandbox mode.
So, if for any reason, you notice programs quitting without crashing, shortly after starting and their window border having a red outline, you're very likely using Avast Antivirus and should deactivate the Sandbox mode.
Happens to me from time to time.
Sometimes closing and opening VS helps, sometimes you have to restart the computer.
I assume it must be related to some DLL or something that is loaded into memory and corrupt, or something like VS loosing the reference to it, and not unloading it correctly/replacing it.
I also once had this strange bug, where I started VS, just like any other day, and my project crashes instantly with some H_RESULT error (some DLL related Error) upon run. After having spent around 1hour searching for the source of the problem, I went into the reference section, and what did I see there : the worst possible circular reference ever : my business project had a reference to ... itself ! The kind of stuff you could not do if you wanted to.
The weirdest part of this, must of been that VS managed to compile the project, and it only crashed while trying to run it ...
After my laptop fell on the floor and its screen was a little damaged, I was able to continue working with it, but failed to build a project of mine. At some point, the system froze, and I was forced to restart the laptop. Ever since, I’m not able to start Visual Studio 2008 or 2010. Moreover, when I do try to start one of the versions, I see no splash screen, and at some point, all running applications stop responding, and I’m forced to restart the laptop.
When I started Visual Studio 2008 with the /SafeMode flag it started OK and worked perfectly, but when I tried it with Visual Studio 2010, I did see a splash screen and the application main window was opened, but then the system got stuck again and forced me to restart.
I use Windows XP SP3, and the addins I recall I have are Visual Assist, IncrediBuild, and Productivity Power Tools for VS 2010 (how can I check what other addins are installed without having Visual Studio running?)
I tried using the /Log flag to find out what’s happening, but there was nothing that seemed related in the generated log.
At the time of the hang, the CPU and memory of the system was low.
The problem happens whether I open Visual Studio with no solution, or with an existing solution.
Do you have any idea why this might happen, or how it can be solved?
Edit:
I run chkdsk /R /V and it is stuck on "1 percent
completed." for hours now. Is there anything I can do?
I'll try to re-install Visual Studio 2010 next week, when I'm in the office. I hope that will help.
Thanks a lot,
splintor
Your drive is torched. Buy a new drive, and salvage whatever you can from the existing drive, then swap them out. If you're lucky you can salvage enough of the existing drive to not need to do a full OS reinstall, but it's likely you're going to need to do some reinstallation.
Looks like the cause if the fall of your laptop. Though what changes happened is unknown it is more likely to be a hardware issue.
Did you reinstall the softwares and check how they work.
If I was diagnosing this issue, I would start from the ground up.
Start of with a basic CheckDisc - CheckDisk Instructions for XP
Progress from that to try re-installing over your existing VS install.
I can't see it being a software problem, so I reckon the checkdisk will discover/fix something, or a reinstall should resolve it.
Dave
You've probably damaged your hard disk in an area which is touched by VS. Windows often grinds completely to a halt when it's struggling to read a damaged area of disk.
Check the Windows event log for errors to do with disk drives.