When hitting F5 to debug a C# .Net Core website the Chrome browser that automatically launches will hang. This started after I upgraded to VS 2022 17.5.2 today (from 17.2 something). I was able to debug fine in the new VS version until it crashes during debugging and VS hung. I closed the browser window and VS and restarted, and from that moment on I have this hanging issue with Chrome.
The Chrome browser will display the starting URL but no response will display and the developer tools network show it is waiting for server response.
If I copy the URL and paste into a new tab (in the same Chrome instance) it will also hang.
If I copy the URL and paste into a new Chrome instance (started from taskbar icon), it will correctly load the page. This other instance is correctly firing breakpoints in my code.
I am using the latest Chrome Version 111.0.5563.65.
I am debugging using IIS Express, in process.
If i put break points in the controller and view i can see them processed, but no response makes it back to the browser window.
I have tried clearing all Chrome caches (several times). I have restarted the computer.
Using "start without debugging" works as expected and the web application runs fine. Obviously this prevents me from achieving any debugging so doesn't resolve my issue.
I am hoping someone knows why the automatically launched chrome browser is not getting a response from the server when debugging? yet other Chrome instances work fine?
Update 3/15/2023 @ 5:22PM Central
The error seems to occur when you hit a breakpoint in chromium browsers (Chrome/Edge). I switched to Firefox and haven't had an issue all day.
Update 3/15/2023 @ 10:22AM Central
Edge just hung after starting/stopping debug multiple times, then modifying code.
Original
We were having issues running debug in Chrome Version 111.0.5563.65 (Official Build) (64-bit) on Visual Studio 2022 for both 17.5.1 and 17.5.2 version. The problem went away once I updated from 17.5.1 to 17.5.2. Between that temporarily fixing the problem and rebooting the computer not fixing the problem, my co-worker figured it may be something hung via caching.
That's when he thought to clear the hidden .vs folder. It was still a temporary fix and needed to be repeated often. @Tobias Andersson and @Slick Van Tanoid answers suggesting trying another browser was a great workaround. I haven't had the issue appear in the Edge browser during debug.
Sorry for adding an answer, I don't have the reputation for commenting or liking answers.