This just started happening and I cannot figure out why. This works fine in firefox, but when using using the debug toolbar in symfony 2.8, it completely locks up chrome. I have to go all the way into my task manager and end the process to get Chrome to close.
Here's a screenshot after waiting 30 minutes. This does not happen in Firefox at all. I've updated Chrome, Symfony, Composer, and every 3rd party library in the application.
I've never seen this before, I'm not even sure where to start troubleshooting this. Any suggestions?
To add, there's no errors being thrown in the server error logs at all. It doesn't appear to be an actual hang on the website, this is additionally confirmed by the toolbar still working in other browsers.
Debugging an ASP.NET MVC application with the default Chrome browser was working fine. I switched the debug over to start up IE instead to do some additional testing and the debugging worked fine. After I was done with IE I switched back to Chrome and now I get this error. If I switch back to IE I also get this error. I have closed and re-opened solution. I have closed and reopened VS. I have run VS with logging and I get no errors in the Activity Log. I can successfully debug if I turn off "Enable JavaScript debugging for ASP.NET" in the debugging options, but it was working fine with that option earlier. Any suggestions?
Go to Tools > Options > Debugging > General and turn off the setting for Enable JavaScript Debugging for ASP.NET (Chrome and IE).
I have also encountered this issue on visual studio 2017 like below:
I have followed below step:
Go to Tools > Options > Debugging > General > Unchecked Enable JavaScript Debugging for ASP.NET (Chrome, Edge and IE).
Once I get rid of check box on Enable JavaScript Debugging for ASP.NET (Chrome, Edge and IE)
Then It works for me and Invalid Pointer error gone!
Unfortunately information on how the debugging emulator works is hard to come by. The only known solutions are...
Reinstall Visual Studio
Update Visual Studio if there is a patch/update available.
You can use a different browser or the internal browser.
So i just updated my CRM 2013 solution to SP 1.
After doing so everything in the solution disappeared except for the Navigation bar as seen on the attached picture.
This only happens in IE where the server is running IE 10. When opening in firefox i am told there is an error but everything is shown.
It might be interesting to tell that the CRM installation is danish. There are no languagepacks installed, and when i inspect the scripts run i can see an invalidcharacterexception in global.ashx.
Does anyone have an idea about what the problem is?
System info: Win 7 x64 SP 1, IE 10, Visual Studio 2010
I've been researching this error all over.
visual studio debug error:
"unable to start program (File path) no more files"
This started with the installation of internet explorer 10 and is happening across all my web projects within Visual Studio 2010.
I've tried all possible solutions (but not VS re-installs) from registry entries (http://forums.asp.net/t/1891930.aspx/1), IE 10 reinstall (fail...won't let me reinstall due to existing version) to switching default launch browser (in Visual Studio, select a different browser such as Chrome to be default browser in "Browse With..." option in project..it works but is pain in the rear) but one thing I just tried which is making me wonder if there is an issue with how IE 10 is launched came from the following experiment:
Basically I did the same process of changing the default browser except that I picked IE 10 x86 version manually in the "Browse With..." option, set it as default and ran project. Voila, it works with no issues.
My next step was to confirm the default IE option in the "Browse With...". I found articles such as (http://lennybacon.com/post/2010/08/22/rehowtochangethedefaultbrowserinvisualstudioprogrammatically) which put me on the path to find out where the settings are for Visual Studios default browser settings.
I checked the browser.xml file and all looked ok including the registry entry pointing to it. I'm unable to check the version of the browser since MS, in it's infinite wisdom decided not to show that info in the Help -> About or anywhere else. so my gut feeling is that the default IE 10 being launched is the x64 bit version.
Does anyone know?
1) how I can confirm the default version of IE 10 launched since afore methods have not worked and
2) why would (I'm assuming) IE 10 x64 launch vs. the defined IE 10 x86 referenced version in the browser.xml file?
Thanks for any and all help.
Dave
UPDATE:
So from doing continual testing, it seems that after I ran the process to change the Default Browser settings in both the registry and the browser.xml file, upon launching the debug process in Visual Studio 2010, it automatically reverted back to the original default broswer settings which would launch the x64 version of IE 10. So in my case, it seems that the issue (error above) lies in the fact that debugging in Visual Studio 2010 using x64 browsers would cause the error. With no recourse, I ended up removing IE 10 from Windows Features and going through a painful process of getting IE 9 back on my system, I now can effectively debug using IE (x86).
It seems that MS is not pursuing any fixes for this issue of the default browser in VS 2010 from what I've read. There are in browser tools I've seen to do the default browser setting changes but don't want to bother with it/don't trust it will work.
Hopfully this helps others dealing with the same pain I have endured...
Thanks
Dave
When I ran into this problem (using IE 11) I noticed that iexplore was open about a hundred times in the task manager. After killing them all I was able to open my project just fine.
Since then, I have made a .bat file with this code: taskkill /F /IM iexplore.exe /T
so now I just run the .bat when I get that error. (alternatively you could run that code from the cmd)
James Butler's response is good for killing all the open IE processes. Which seems to be the issue here. The best solution I have been using is to just set, "Don't open a page. Wait for a request from an external application." then I just refresh the URL (if already open in browser) each time I rerun the debugger.
Access in Project properties under the, "Web" option. Then change setting there.
Check the following registry key
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\TabProcGrowth
Make sure that the value is Minimum
I started getting this error today after restarting from a Windows Update. I'm on Windows 8.1 desktop using VS.NET 2013. To fix I had to add another browser choice in VS debug that was pointing to the x86 version of IE11, and set that as the default. Although the post alludes to the x64 vs x86 browsers being the issue, this seems like an easier solution than the original poster's process of uninstalling and reinstalling browsers.
This blog explains how to set the default browser for debugging to IE x86: http://weblogs.asp.net/gurusarkar/visual-studio-web-developer-express-starting-two-instances-of-internet-explorer-and-throwing-an-error
Have you tried this: "...try selecting the project node in Solution Explorer and choose Set as StartUp Project". Just worked for me.
https://social.msdn.microsoft.com/Forums/en-US/efd93f22-1f1f-4fb1-8ff3-e29104780572/unable-to-start-program-there-are-no-more-files?forum=lightswitchgeneral
I think this is caused by a more general issue of low available system memory. In my case, Performance Monitor showed I was using 82% of my available memory when I was receiving the error. Looking at the processes, the culprit for me was lots of Chrome processes. I shut down Chrome, which freed up about 2 GB of memory, and then I was able to run the debugger successfully. Shutting down lots of IE processes would achieve the same thing of freeing up lots of memory. So I think the solution is just to free up system memory by shutting down whatever processes you don't need open.
This is what is working for me with windows 11 and edge:
Project Start Options - Don't open a page. Wait for a request from an
external application.
Start - Local IIS (Microsoft Edge)/Script
debugging disabled
Create a shortcut to launch the application like
this: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
http://localhost/MyApplication/
I have an ASP.NET MVC 3 app. It is working fine in both IE8 & FF when we run VS2010. I have deployed this code in IIS 7.5. Now, the deployed app is working fine in FF, but not in IE8. I am getting error:
Stop running this script?
A script on this page is causing Internet Explorer to run slowly...
See following screen-shot:
I tested the published code in IIS6, It's working fine in both FF and IE8.
Any help is appreciated.
You are probably using some javascript which is entering a loop of some sort (possibly recursion)
Either comment out one function at a time to see which function is the culprit, or do it in binary-search fashion and comment out half at a time to narrow it down.
Finally, is there something out of the ordinary about your page? If the your javascript (or one of your libraries) was not the culprit, start ripping out chunks of your code to narrow the problem down.
Unfortunately there is not a quick answer to this one...
There are various ways to try to determine what's going on with your JavaScript. Try reloading the browser. You can also try downloading the Ajax profiling bits at
http://archive.msdn.microsoft.com/AjaxView
This can help determine your slow functions. You could also load up the JavaScript debugger and break into the code as well
What nonstandard javascript libraries are you running? Any?
Since your app runs differently seemingly only based on iis version differences compare a session on one to a session on the other using 'Fiddler'