"Should not already be working" in Firefox after a breakpoint/alert · facebook/react#17355

(132 留言) (85 反應) (0 負責人)JavaScript (245,029 star) (51,039 fork)batch import

Difficulty: mediumType: BugType: Needs Investigationgood first issue

描述

Do you want to request a feature or report a bug? Bug

What is the current behavior? I'm seeing "Error: Should not already be working" after upgrading to React 16.11

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

This is exclusively happening on an older version of Chrome, 68.0.3440 on Windows 7

I was unable to reproduce this in a VM environment but our Sentry is getting littered with these errors.

I know it's a long shot, but I wasn't able to find any information about this error anywhere, just a reference in the error codes file in react, so thought it would be a good idea to report this just in case. Curious if anyone has seen this.

貢獻者指南

技術棧: javascriptreact
領域: frontend
議題類型: bug
難度: 4
預計時間: over 1 week
活動狀態: stale
清晰度: mostly clear
前置要求: React fiber internalsReact error handlingBrowser debugging
新手友善度: 20
研究方向: Investigate the error message 'Should not already be working' which is defined in the React error codes file (likely scripts/error codes.json). Look into the React fiber scheduler code (e.g., ReactFiberWorkLoop.js) to understand when this invariant is triggered. Reproduce using the reported conditions in older browsers (Chrome 68 on Windows 7). Check if there were any related commits or PRs addressing this error in later versions. Consider if this is a race condition with breakpoints/alert. Also review the comments in the issue for troubleshooting attempts and potential fixes.