Launching/Reloading Chrome debugger with a Breakpoint hangs

John Twigg
2023-03-16T20:55:33Z

<!--
Please note that your issue will be fixed much faster if you spend about
half an hour preparing it, including the exact reproduction steps and a demo.

If you're in a hurry or don't feel confident, it's fine to report bugs with
less details, but this makes it less likely they'll get fixed soon.

In either case, please use this template and fill in as many fields below as you can.

Note that we don't provide help for webpack questions after ejecting.
You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

The chrome debugger will hang when launched with `react-scripts start` **when there is a breakpoint enabled**

Launching 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?

<!--
Your module tree might be corrupted, and that might be causing the issues.
Let's try to recover it. First, delete these files and folders in your project:

* node_modules
* package-lock.json
* yarn.lock

Then you need to decide which package manager you prefer to use.
We support both npm (https://npmjs.com) and yarn (https://yarnpkg.com/).
However, **they can't be used together in one project** so you need to pick one.

If you decided to use npm, run this in your project directory:

npm install -g npm@latest
npm install

This should fix your project.

If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install).
Then run in your project directory:

yarn

This should fix your project.

Importantly, **if you decided to use yarn, you should never run `npm install` in the project**.
For example, yarn users should run `yarn add <library>` instead of `npm install <library>`.
Otherwise your project will break again.

Have you done all these steps and still see the issue?
Please paste the output of `npm --version` and/or `yarn --version` to confirm.
-->

No applicable

### Which terms did you search for in User Guide?

<!--
There are a few common documented problems, such as watcher not detecting changes, or build failing.
They are described in the Troubleshooting section of the User Guide:

https://facebook.github.io/create-react-app/docs/troubleshooting

Please scan these few sections for common problems.
Additionally, you can search the User Guide itself for something you're having issues with:

https://facebook.github.io/create-react-app/

If you didn't find the solution, please share which words you searched for.
This helps us improve documentation for future readers who might encounter the same problem.
-->

chrome, breakpoint, hang

### Environment

<!--
To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
This enables the maintainers quickly reproduce the issue and give feedback.

Run the following command in your React app's folder in terminal.
Note: The result is copied to your clipboard directly.

`npx create-react-app --info`

Paste the output of the command in the section below.
-->

```
Environment Info:

current version of create-react-app: 5.0.1
running from /Users/john.twigg/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

System:
OS: macOS 13.2
CPU: (10) arm64 Apple M1 Max
Binaries:
Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.17.0/bin/yarn
npm: 7.24.2 - ~/.nvm/versions/node/v16.17.0/bin/npm
Browsers:
Chrome: 111.0.5563.64
Edge: Not Found
Firefox: 110.0.1
Safari: 16.3
npmPackages:
react: ^18.2.0 => 18.2.0
react-dom: ^18.2.0 => 18.2.0
react-scripts: 5.0.1 => 5.0.1
npmGlobalPackages:
create-react-app: Not Found
```
### Steps to reproduce

<!--
How would you describe your issue to someone who doesn’t know you or your project?
Try to write a sequence of steps that anybody can repeat to see the issue.
-->

Very easy repro stepss

1. `npx create-react-app test-debug`
2. `npm i`
3. To the `App.js` I added a button to simplify breakpoint invocation.
```
{
console.log("you clicked")
}}>Click Me
```
4. **Ensure no breakpoints are enabled**
5. Run `npm run start` to launch with `react-scripts start`
6. Launch a VS Code's Debug configuration to launch `chrome` debugger

```
{
"type": "chrome",
"request": "launch",
"name": "Launch Chrome against localhost",
"url": "http://localhost:3000",
"webRoot": "${workspaceFolder}"
}
```
** The CRA launch page should load normally in the debug Chrome browser**
7. Verify reloading the page worked in the debugging browser.
** The CRA launch page should load normally in the debug Chrome browser**
9. Add a breakpoint on the `console.log("you clicked")`
10. Reload the page
** The page will hang when trying to reload **

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

<!--
How did you expect the tool to behave?
It’s fine if you’re not sure your understanding is correct.
Just write down what you thought would happen.
-->

* 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

<!--
Did something go wrong?
Is something broken, or not behaving as you expected?
Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->

Hangs and spins indefinitely.

![image](/uploads/c64c5a5712dcb927e240e66715363d29/224766632-e52f3b38-479e-4601-ae2f-63812ee4ee1b.png)

### Reproducible demo

<!--
If you can, please share a project that reproduces the issue.
This is the single most effective way to get an issue fixed soon.

There are two ways to do it:

* Create a new app and try to reproduce the issue in it.
This is useful if you roughly know where the problem is, or can’t share the real code.

* Or, copy your app and remove things until you’re left with the minimal reproducible demo.
This is useful for finding the root cause. You may then optionally create a new project.

This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
Once you’re done, push the project to GitHub and paste the link to it below:
-->

(Paste the link to an example project and exact instructions to reproduce the issue.)

<!--
What happens if you skip this step?

We will try to help you, but in many cases it is impossible because crucial
information is missing. In that case we'll tag an issue as having a low priority,
and eventually close it if there is no clear direction.

We still appreciate the report though, as eventually somebody else might
create a reproducible example for it.

Thanks for helping us help you!
-->