Bug: in chrome version 127.0.6533.100 and the previous release, debugger hangs on breakpoint, when attempting to interact with values

[KellyGrantSDSU]

Starting with the version ending in .88 and in 127.0.6533.100, the react devtool plugin hangs when a breakpoint is hit and you attempt to hover over any variables in the current scope, where the break happened. You can briefly scroll the right panel with the mouse wheel, but fairly soon that goes away too. If you immediately press continue, the code continues to run. Otherwise, you have to press F12 to remove the debugger and press F12 again to restart it. The other tabs seem to function normally, but the ability to set breakpoints and inspect elements is very broken

React version: Extension 5.3.1, react 17.02

Steps To Reproduce

1. Set a breakpoint
2. Reach the breakpoint.
3. Attempt to inspect elements in the current scope.
4. Find the debugger is now hung and will not interact with the mouse.

I don't have a code example, it doesn't seem to be dependent on any particular code, it behaves the same in every part of our application; set a breakpoint, hit it, and you are stuck.

The current behavior

Debugger hangs upon stopping at a breakpoint

The expected behavior

Debugger allows user to inspect code and variables when hitting a breakpoint.

[woowalker]

i think it was caused by chrome, when i downgrade to version 121.0.6167.86, it work perfect. by the way, the latest version of chrome 127.0.6533.120 still got this problem. you can find older verison in here

[KellyGrantSDSU]

I'm curious if the fact we are behind in React (17.02) is causing the issue, that they have reached a milestone where they don't support it within the debugger. But the devtools have not changed while Chrome has, so it may be a simple incompatibility with Chrome now. Makes me sad, I"m using Firefox now because I have to have the ability to debug. We can't upgrade React because we still have some Enzyme unit tests, plus I believe we have to fix other things to upgrade.

[suchenrain]

same issue in Chrome 127.0.6533.120 and Edge 127.0.2651.105, but someone said it works fine in Chrome Beta here. Not sure if this is caused by the Chromium ?

[juampipardal]

Same issue here. Using Chrome canary in the meantime. Version 127.0.6533.120

[ELPona]

Still happenning, both Chrome and Edge.

[github-actions[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!