Chrome restore pages message when debugging ASP.NET

Reported by Gerard Frantz May 10, 2017 at 11:20 AM aspnet5 Fixed-in: Visual Studio 2017 Version 15.3 Visual Studio 2017 version 15.1 windows 10.0

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.

Add comment Show 11

Richard Scholten · May 12, 2017 at 12:02 PM 0

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.

Michael Braude [MSFT] · May 25, 2017 at 05:14 PM 0

Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!

Richard Scholten · Jun 01, 2017 at 10:04 AM 0

@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.

Michael Braude [MSFT] Richard Scholten · Jun 01, 2017 at 05:06 PM 0

@Richard Scholten sorry I do not have a release date for you. It will be in a preview channel soon.

Neville Perkins · Jul 13, 2017 at 11:18 AM 0

I just updated to 15.2 (26430.15) and it is showing the annoying "Restore pages?" pop-up.

Gerard Frantz · Aug 22, 2017 at 09:15 AM 0

Latest update (15.3.1) fixed the issue for me.

Diego Geffner · Sep 25, 2017 at 09:19 PM 0

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!

Gerard Frantz · Sep 26, 2017 at 12:23 PM 0

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).

AJ Saulsberry · Sep 29, 2017 at 06:45 PM 0

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).

Dhanvi Kapila AJ Saulsberry · Sep 29, 2017 at 08:29 PM 0

Thank you for your feedback. We are working on a fix and will post updates when we have it ready.

Diego Geffner · Oct 04, 2017 at 05:47 PM 0

Thank you for your feedback! Your detailed description of the way to reproduce the issue was very helpful, and we were able to identify what was happening. We have fixed the problem in an upcoming release (Visual Studio 2017 15.6). Thank you for helping us build a better Visual Studio!

Added a solution by Graham O'Riley · May 24, 2017 at 08:04 AM

Same issue with vs2017 and Chrome Version 58.0.3029.110 (64-bit)

Add comment Show 3 · Share

graham.oriley · Sep 19, 2017 at 09:25 AM 1

I still get this and I am using the latest version of vs: 15.3.3

VL · Apr 18 at 02:39 PM 0

Reporting that I am still getting this with VS2017 15.5.3 and Chrome 65.0.3325.181

Roi Chen - MSFT ♦ VL · Apr 23 at 09:50 AM 0

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.

Added a solution by Blair Wang-MSFT · Aug 15, 2017 at 03:29 AM

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.

Add comment Show 3 · Share

Richard Scholten · Sep 04, 2017 at 01:59 PM 0

I can confirm that the latest update fixed the issue.

Thanx for the support

graham.oriley · Sep 19, 2017 at 09:31 AM 0

I still get this and I am using the latest version of vs: 15.3.3

Kevin Davis · Sep 19, 2017 at 11:29 AM 0

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.

Added a solution by Chris Wells [MSFT] · Sep 29, 2017 at 06:11 PM

Thank you for your feedback! We have fixed this issue and it's available in all VS 2017 updates newer than 15.3.1.

Thank you for helping us build a better Visual Studio!

Add comment · Share

Added a solution by Diego Geffner · Jan 03 at 07:40 PM

Thank you for your feedback! We have fixed this issue and it's available in Visual Studio 15.6. Thank you for helping us build a better Visual Studio!

Add comment · Share

Added a solution by Isaac M. · Jun 03, 2017 at 05:06 PM

I was able to work around until update is available by doing this.

Edited file:

"%UserProfile%\AppData\Local\Google\Chrome\User Data\Default\Preferences"

and changed:

"exit_type": "Crashed"

"exit_type": "normal"

and then restarted all instances of Chrome.

Add comment · Share

Developer Community

Get help from our community supported forum

Chrome restore pages message when debugging ASP.NET

Solutions

Try Microsoft Edge

Developer Community

Get help from our community supported forum

Chrome restore pages message when debugging ASP.NET

Solutions

Related Problems