Open john-twigg-ck opened 1 year ago
I have got exactly the same issue on an existing project. Windows 10, on either Node 16.15.0 or 18.15.0, with a single breakpoint not possibly reachable during reload.
I'm getting this bug on a custom asp.net application and a vanilla create-vite
. Both using vscode, with "debugWithChrome"
in the launch.json
Starting about 2 weeks ago. May be a chrome issue?
See https://stackoverflow.com/questions/75740738/chrome-hangs-when-debugging-in-visual-studio-2022
Looks like it's fixed or a fix is incoming.
Describe the bug
The chrome debugger will hang when launched with
react-scripts start
when there is a breakpoint enabledLaunching with no breakpoints enabled will succeed, however when a breakpoint is hit, subsequent
Reload
's of the page will cause the browser load to hang. There's no console output.Did you try recovering your dependencies?
No applicable
Which terms did you search for in User Guide?
chrome, breakpoint, hang
Environment
Steps to reproduce
Very easy repro stepss
npx create-react-app test-debug
npm i
App.js
I added a button to simplify breakpoint invocation.npm run start
to launch withreact-scripts start
chrome
debuggerThe CRA launch page should load normally in the debug Chrome browser
console.log("you clicked")
NOTE: Removing the breakpoint now does nothing. The session is corrupted. NOTE: Variations are to launch with a breakpoint enabled, and it hangs as well. NOTE: Verified on 2 mutually exclusive computer setups.
Expected behavior
Reloading debugger with a breakpoint enabled should not hang the debugging session. Especially when the breakpoint is not likely hit, like in a click handler.
Reloading with a breakpoint on launch should invoke the breakpoint.
Actual behavior
Hangs and spins indefinitely.
Reproducible demo
(Paste the link to an example project and exact instructions to reproduce the issue.)