I work on visual studio 2013, and in recent days every time I right click inside c# file I get message: "visual studio 2013 stopped working".
I tried to repair installation, but did not work.
in the event viewer I found the error:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception. Exception
Info: System.AccessViolationException
in google search I did not find something except of reinstall visual studio, but I prefer avoiding it.
if you have 2 graphic processors on PC :
switch (graphic.card.name on my PC)
{
case "Intel " : VisualStudio.Crashed();
RightClickMouse on VS.ShortCut
Select("Run with graphic processor");
Click on morePowerfulProc :-)
BeHappy;
break;
case "NVIDIA" : VisualStudio.WorkingGood(); break;
}
i have two graphic processors on my PC. I don't know why but any VisualStudio working correct only with Nvidia graphic card;
Related
I've recently updated my copy of visual studio 2013 to update 5 in the hope I could start using the Performance and diagnostics hub but I get the following message in the options menu.
There were no error messages from update 5 installation. When I open the application (even a administrator) I don't have the menu item "performance and diagnostics" and I have already tried to repair the installation.
Before I received the following error message, checking the activity log the error was something about duplicate ID's (Can't share the exact wording as it's not in the log anymore)
Can anyone help?
Thanks
This is the second time I've seen the error "Scripted Sandbox64.exe has stopped working" in Visual Studio 2015.
In my particular case, I was building a Windows Forms application and you place the application into the system tray in Windows. This application also writes files using System.IO. The project has nothing more than that. Visual Studio 2015 Community Edition crashes.
Disable the Diagnostic tool under
Tools -> Options -> Debugging -> General -> Enable Diagnostic Tools while debugging
More information: https://stackoverflow.com/a/31904957/2856307
Just adding the information that #Bahien Nguyen provided in his answer.
Reference:
http://www.expertdebugger.com/2016/01/19/how-to-fix-visual-studio-2015-error-faulting-application-name-scriptedsandbox64-exe-has-stopped-working/
How to fix Visual Studio 2015 error Faulting application name ScriptedSandbox64.exe has stopped working
I am trying to debug a windows application in Visual Studio 2015. I have already installed the latest updates. After the debugging starts, I get the following pop up error ScriptedSandbox64.exe has stopped working A problem caused program to stop working correctly.
The event viewer is showing the following details
Faulting application name: ScriptedSandbox64.exe, version: 14.0.24720.0, time stamp: 0x564e98d0
Faulting module name: ScriptedSandbox64.exe, version: 14.0.24720.0, time stamp: 0x564e98d0
Exception code: 0xc0000602
Fault offset: 0x000000000000f933
Faulting process id: 0x51c
Faulting application start time: 0x01d152888b333a1c
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ScriptedSandbox64.exe
Faulting module path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ScriptedSandbox64.exe
Report Id: 029bb0e0-771e-4046-bbc1-2c69686f144a
Faulting package full name:
Faulting package-relative application ID:
IDE gets locked up due to this and the only option is to click on close program.
Solution
This process is launched during debugging. Stop Visual Studio debugging session.
Disable the Diagnostic tool under Tools->Options->Debugging->General disable the option Enable Diagnostic Tools while debugging
Debugger still works after unchecking the above option.ScriptedSandbox64.exe no more throws any errors.
Dear Reader,
Please share your feedback about this article . This will enable me to improve this for the benefit of other readers.
Solution for now is to install Visual Studio 2013 Community Edition and retrofit the project by changing the *.csproj file XML.
For anybody who has this problem:
I experienced the same problem debugging a WPF application today in VS2015 Community Update 2. I am sure that I did not have this before but I dont know how it crept back in. As mentioned before, disabling the Diagnostic Tools solves the problem. Unfortunately, this is not an option for me. Luckily, installing the "Update for Microsoft Visual Studio 2015 Update 2 (KB3151378)" solved the problem for good. Link: https://msdn.microsoft.com/en-us/library/mt695655.aspx?f=255&MSPPError=-2147217396
I had a very similar issue, same dialog as OP posted, but then I encountered the same when running the application in debug mode. That helped me find what was causing this error in my application.
I traced it down to an iteration through DataGridViewRows, which would contain about 1800+ rows. My iteration was to set a checkbox value to true, but I ended up not needing to do that anyways. Once I removed this, the application would run okay.
Came to work this monday and started up Visual Studio 2013 and it says my license has expired and I need to sign in to extend it, but when I press the sign in button VS crashes and says "Microsoft Visual Studio 2013 has stopped working".
I've tried repairing my installation of VS but I get the same error.
I've tried running VS in safe mode but I get the same error.
I've tried debugging VS and found this message "An unhandled exception of type 'System.ExecutionEngineException' occurred in Microsoft.VisualStudio.Services.WebApi.dll" but I find nothing relevant when googling it.
Any suggestions are on how to fix this are welcome. I've had this version installed since it came out and I have a license for it. And I've signed in before without problems.
I'm building a project in Visual Studio 2010 and the build fails because it cannot copy the assemblyname.dll file from obj to bin folder. The exact error message is:
Error 7
Unable to copy file "obj\Debug\AssemblyName.dll" to "bin\AssemblyName.dll". The requested operation cannot be performed on a file with a user-mapped section open.
I think this is because the previous file in bin-folder is not accessible. When I try to delete the file manually, I get an error "The action can't be completed because the file is open in another program". If I try to see what application locks the file with Unlocker, I don't get any results (No Locking handle found).
If I restart Visual Studio, the error goes away but happens again after a build or two. Goes without saying that this is seriously slowing me down. Any advice how to start solving this?
VIsual Studio 2012 on Windows 8. I was receiving the same error message on my project. Restarting Visual Studio or cleaning the obj folder manually did not help. Finally I closed all open files (Windows -> Close All Documents) and the problem went away.
This behavior was due to a newly installed Visual Studio extension called Visual Studio Achievements (http://visualstudiogallery.msdn.microsoft.com/bc7a433b-b594-48d4-bba2-a2f24774d02f)
I noticed that the .pdb file was locked by FxCop (using Unlocker) and I think that the Achievements -extension uses it. After disabling the extension I've no longer got the error mentioned above.
This bug has been fixed in recent versions of the extension (>1.7). It was released as a beta, btw...
This behavior of VS happen very often even on my computer (and on computers of my coworkers).
In my experience it happen more frequently when:
I have some form opened in design when i compile
I stop the execution od the application by pressing the "stop" button
in VS instead of exiting the application
So, closing the form in design before compile, and exiting the application instead of stopping it, somewhat mitigate the issue... but it still happen :-|
My computer is Win 7 x64 SP1 with VS 2010 SP1, 8Gb ram, and no swap file
Platform: Windows 8 Pro, Visual Studio 2012
I found that I receive this error when I am accessing the folder in Windows Explorer.
I was creating PDF documents with Visual Studio 2012. To review the sample document I would right click in Solution Explorer and use Open Folder in File Explorer.
On Windows 7 I would get a SYSTEM.IO error if the actual PDF document was open in Adobe Reader which is expected. With Windows 8 I found that I receive the above error if I have the folder open. I suspect there is a conflict with the Windows 8 preview.
If I close the folder and run the program it works fine.
Check if you open the dll in visual studio.
I open the dll in visual studio and this error happen!!
I create their basic Flash app with their Flash IDE for Visual Studio 2010
http://www.sapphiresteel.com/Products/amethyst-ide/article/amethyst-product-page
When launching the run button, it launch flash but with this error within Flash CS4:
The following JavaScript error(s) occurred:
At line 6 of file "FlashApplication1.jsfl":
Cannot find file file:///C:/temp/FlashApplication1/FlashApplication1/FlashApplication1.as.
Did someone tried and has this problem also and then a solution ?
This is discussed in a thread in the SapphireSteel Software forum: http://sapphiresteel.com/forum/index.php?topic=542.0