Issue 1:
I'm currently updating the new React DevTools to use suspense for more interactions (bvaughn/react-devtools-experimental#196). This has uncovered three pain points that we should try to address:

Using the "two setState pattern" can be awkward if the priority is "normal" or higher (as was the case in my "keydown" event handler) because scheduler.next uses "normal" priority for this case. (This also applies to e.g. non-React event handlers, since the default priority for these is "normal" as well.) Temporary workaround - manually run the first update with user-blocking priority.

Offscreen updates cause user-blocking and normal priority work to be batched together (for unknown reasons). This makes interactions feel unresponsive. Temporary workaround - none (other than to stop using offscreen priority).

Fallback UI shown too quickly. One of the main reasons to use suspense in the "inspected element" panel to begin with is to avoid a quick flash of the "Loading..." fallback when a new element is selected. However, it seems like this is still happening even with suspense. Temporary workaround - none, since I don't know the cause.

Edit I think the first two items I reported were caused by a second/duplicate scheduler package that had gotten installed in DevTools as a transient dependency.

Issue 2:
Describe what you were doing when the bug occurred:

Clicked record before firing off the onClick function

When I clicked stop recording this error was thrown.

Please do not remove the text below this line

DevTools version: 4.7.0-23309eb38

Call stack: at N (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:164298)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163705)

at e.getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:166664)

at Ul (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:342328)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:62450)

at tl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:71793)

at zl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:113765)

at Ic (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:104502)

at Tc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:104430)

at Dc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:104298)

Component stack: at Ul (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:342099)

at div

at div

at div

at Co (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:263571)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:366677

at n (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:276314)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:278724

at div

at div

at Xi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:325177)

at Ge (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:207026)

at sn (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:216342)

at Va (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:293773)

at us (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:371869)