- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Get help from our community supported forum
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
Chrome restore pages message when debugging ASP.NET
I debug an ASP.NET application using the Google Chrome browser. If I stop the debugging session from Visual Studio (stop debugging), Chrome is closed by Visual Studio. The next time I start debugging, Chrome displays an annoying message: "Restore pages? Chrome didn't shut down correctly" that I have to manually dismiss. If I stop the debugging session by closing Chrome, no message is displayed. I would appreciate if Visual Studio to properly closed Chrome so that this message is not displayed.
Same problem here when using chrome. Also every now and then Visual Studio "hangs" and the debugger wont stop. after a minute or so a popup asks to stop the debugging.
Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!
@Michael Braude [MSFT] Thats great to hear! Can you tell us in what upcomming release the fix will be? I just updated VS with the latest release (Release Date: May 30, 2017 - Visual Studio 2017 version 15.2 (26430.12), but the problem is still there. Fix is not mentioned in the release notes.
@Richard Scholten sorry I do not have a release date for you. It will be in a preview channel soon.
I just updated to 15.2 (26430.15) and it is showing the annoying "Restore pages?" pop-up.
Thank you for your feedback! I tried to reproduce this issue myself on Visual Studio 15.3.3, but I wasn't able to reproduce it, so I'm going to need more information to figure out what is happening. For us to investigate this further, could you please provide us this information:
- Could you please tell us which kind of ASP.NET Project are you using when this happens (WebSite, ASP.NET Core Web Application (.NET Core), ASP.NET Web Application (.NET Framework, etc...))?
- Could you please test if this issue also reproduces if you create a new empty project from the same type of project you are using?
- Could you please test if this issue happens if you try this after the PC has just been restarted, and no other instances of Chrome are running?
- Finally, Could you please post the messages that appear on the Output Window while using the option "Show output from Debug" after this issue happens? I'm looking for some messages that say something like this:
The program '[<some_pid>] chrome.exe: WebKit' has exited with code <some_number_1> (<some_number_2>). The program '[<some_pid>] chrome.exe' has exited with code <some_number_2> (<some_number_4>).
We look forward to hearing from you!
1. ASP.NET Web Application (.NET Framework), using MVC
2. Yes it does
3. I Did not try (see below)
4. The message is the same, with or without the issue:
The program '[3608] chrome.exe: WebKit' has exited with code -1 (0xffffffff).
In fact, I found a way to replicate systematically:
- Create a new ASP.NET Web Application (.NET Framework), using MVC
- Launch with F5
- In Chrome, press F12 to open the developers tools
- In VS, click the red square icon to stop debugging
- Press F5 again: the issue is there
The issue doesn't take place if you don't open the developers tools (I think it did in previous versions of VS).
This is still occurring in 15.3.5, except that it doesn't matter how Chrome is shut down (directly or by ending execution in VS).
Thank you for your feedback. We are working on a fix and will post updates when we have it ready.
We are aware of this issue in the latest version of the debugger. The fix for this issue is not working after we made few improvements to other parts of the JavaScript debuggers. We will prioritize this issue based on the feedback here to make sure we have a fix that works.
Yes, one year after, it's still there. This ticket should be reopened.
I still get this and I am using the latest version of vs: 15.3.3
Reporting that I am still getting this with VS2017 15.5.3 and Chrome 65.0.3325.181
Hi VL, Can you create a new report by using Report A Problem in Visual Studio (It's on the Help Menu under Send Feedback)since this issue has been closed for a long time? Thank you for your patience.
I can confirm that the latest update fixed the issue.
Thanx for the support
I still get this and I am using the latest version of vs: 15.3.3
I can confirm that the latest update has NOT fully fixed this issue (still seeing in 15.3.3). It isn't as big of an issue because it has forced me to change my habits, closing Chrome instead of exiting the debugger from VS more often, but it's still an annoyance.
175 People are following this
