When I open the visual studio 2010 premium, Solution explorer doesn't show up.
It was working and now its not.
It is showing a out of memory exception. Any help would be greatly appreciated.
Attached is the screen shot
try resetting visual studio by closing it out completely and running the following command.
devenv /resetsettings
I would recommend submitting this to https://connect.microsoft.com as a bug.
They will most likely ask for more information.
This exception can have more than one cause. It isn't very likely that Visual Studio is actually running out of memory, the system might be running low on resources. The desktop heap is one of them. A simple reboot will fix that.
If this reoccurs, use Taskmgr.exe to try to find the processes that are hogging resources. View + Select Columns, tick Handles, USER objects and GDI objects. If it is Explorer then you have a misbehaving shell extension handler.
Related
When I try to start it. The loading screen flash by in 1 millisecond then dissapear. Iv'e tried the devenv.exe /Setup solution, but devenv.exe won't start either.
Don't know what to do! I think it has something with to do with devenv.exe. Because after I used the selector, it has been corrupt.
Assuming you've already tried the basics (turning it off and turning it back on again, etc.), you may want to try running it as administrator. Right-click>Run As Administrator
I've had some issues on and off with VS not always working for me unless I run as admin.
If that fails, you can repair the installation by going through the Programs and Features menu.
After opening project (new or old) Visual Studio shows warning "Designer terminated unexpectedly" (can see in the picture below). What could cause this error? And how to fix that?
I clicked "click here to reload the designer" and it shows the same error.
I had the same issue and found out that my Oracle VirtualBox causes the issue.
My Visual Studio runs in a virtual Windows 10 enviroment.
After I disabled "Enable 3D Acceleration" in options Display, my Visual Studio Designer worked fine again.
I just had a similar problem. Tried:
Clicking to reload the designer
Cleaning my solution
Restarting Visual Studio
Repairing Visual Studio
Uninstalling and re-installing Visual Studio!
It ended up being graphics related, as you mentioned.
I have hybrid graphics (Intel and NVIDIA), and was using NVIDIA for Visual Studio. Changed it to Intel and this worked.
If it helps, a screenshot of my NVIDIA control panel is below:
Before (broken):
After (working):
Some people have found a file "c:\program" that causes this, often created by typo creating a log file.
Check to see if this file exists, and if so, move or delete it.
Graphics card was the problem for me. I have an external USB video from DisplayLink and when I disconnected it the problems went away. in fact it didn't return when I reconnected the displaylink.
Start Visual Studio As Administrator~!
I had the same problem when i started working in Team Projects, so almost everything did not work including the designer, properties menu, debugging and so on.. (which is totally unusual for anything to cause all these problems except for Administrator Privileges issues probably in most cases).
Don't know why or what caused it, but at least it works.
In my case it was the problem with using system brushes as ThemeResource. Yes this is apparently a bug like other odd bugs in MS products. So I had to comment out them until I finished my project. I don't know, maybe another factor such as my graphic hardware was not ineffective but this does not exonerate MS.
I have problem with Visual Studio 2010 on Windows 7 64-bit. After some time of work VS starts consuming ~50% CPU and UI responding slows down. When I close VS then UI disappear but process stay.
When I forgot to kill those hung processes at the end of day, I will end up with numerous devenv.exe processes.
I have reinstall Visual Studio and reinstall Windows and ended up with the same problem... doesn't change anything. Please help. :/
Remove and/or uninstall all third-party Visual Studio add-ins and extensions. Disabling is not good enough.
Visual Studio 2010 relies heavily on graphics. Therefore:
Update your video driver.
Turn off "Enable rich client visual
experience"
Turn off "Use Hardware graphics acceleration if
available"
There are also temporary files that Visual Studio uses that may need to be cleared out.
Clear out your %temp% folder.
Clear out %AppData%\Local\Microsoft\WebsiteCache
Clear out %AppData%\Local\Microsoft\VisualStudio\10.0\ProjectAssemblies
Your project and solution user settings may be corrupt due to so many "crashes".
Delete .user and .suo files (you will lose the startup project, bookmarks, breakpoints, and other user settings specific to projects and solutions.)
Begin where you began before - it may seem overkill but this is the only way to be sure we are addressing everything short of hardware issues.
Reinstall Windows - make sure you are using a validly licensed copy, and patch the hell out of it before installing Visual Studio.
Note: I doubt it is a GPU driver issue, but it never hurts to use the most up to date driver and this is the place to do it right after a fresh OS install.
Install Visual Studio .Net 2010 but do not start it up. Let it get the frameworks installed fresh.
Use Windows Update to install the VS 2010 SP1 patch, and any/all patches for .Net frameworks.
Make an images for yourself right here so you have something to build from if you need to try this again. It will save you lots of time.
Fire up Visual Studio, and test your closing before installing anything else.
If it does not work here, there's likely some conflict between PC hardware and window OS, and you should try to find this symptom in other applications to get more info.
Here's what i would be looking for:
Does it happen EVERY TIME?
Does it happen after you debug your project ? does it happen for ALL projects?
Does it also happen when you don't load any projects? (simply start the IDE and wait).
Does it happen after a debug session of your application? maybe the application is not closed properly?
Do you have any other apps running at the same time that may cause this? try reproducing with a minimal set of apps/services running.
What are you doing exactly when it starts freezing ? anything in particular?
I would try to get 2-3 memory dumps at the time of hanging, post it here as well as to MSFT people. That would be a good start.
A few days ago, the attach button in "Attach to process" dialogue became disabled in VS 2010 and VS 2008 likewise. At first I thought that it is just an extension I've installed in VS 2010 but then I noticed it is the same in VS 2008. The both VS's a re running in administrative mode and on Windows 7.
I looked around but I can't seem to find a solution to this.
If anybody has encountered an similar problem, a little help would do great.
Thanks upfront.
EDIT: Attached a picture of the dialogue!
Where it says
you should press 'Select' and ensure at least managed is ticked. (or choose automatic)
otherwise, the 'Attach' button will be disabled.
It could also be because there is already another debugger attached to the process - probably the currently running instance of Visual Studio but it may be another instance of Visual Studio, or another debugger entirely (such as WinDbg or a remote debugging session).
Check the "Processes" window (usually found under Debug -> Windows -> Processes) to see what processes Visual Studio is debugging.
Try stopping Visual Studio but don't close the process.
I have come across a weird situation under which Attach button was disabled. This was because of DebugDiag. Please refer the following thread for info.
I was trying to debug a windows service as described here and had the same issue. The solution was to run Visual Studio as Administrator and select to see processes from all users.
Any time i try to debug in visual studio 2008 my entire system will freeze whenever a breakpoint is hit.
I can move the mouse around and that remains responsive but nothing i click on does anything,
I can bring up the task manager but can't do anything with it and i am able to lock/unlock the machine.
I tried a fix that i found via google that suggested i disable advanced text services but it didn't work. I am using visual studio 2008 with SP1 running on Windows XP Pro, asking here is my last hope before formating/reinstalling so i hope someone can help me out.
I debug by running the application in debug mode, the freeze happens no matter what the project size and it seems as if it is just the entire GUI that freezes, the computer carries on working just fine i just can't do anything with it because the GUI is totaly unresponsive.
I found I only had this issue when I was using the keyboard to debug. If I used the toolbar debug buttons, I didn't have an issue.
To "fix" this, I set the LowLevelHooksTimeout to 300ms (from 5000ms). You may need to add the DWORD if it isn't already there.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\Control Panel\Desktop\LowLevelHooksTimeout
HKEY_CURRENT_USER\Control Panel\Desktop\LowLevelHooksTimeout
Restart after making this change for good measure.
How big is the project you are running? When I did a Find last night on a huge open source project, I got kind of the same behavior.
Also, did you try Uninstalling just VS2008, then Reinstalling with only the options you use.
Have you tried disabling "Call ToString()" debugger option? This is ON by default, and is known to deadlock.