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

Started profiler recording

Expanded an accordion control

Collapsed same control

Stopped the recording

The error showed up

Please do not remove the text below this line

DevTools version: 4.11.0-39713716aa

Call stack: at updateTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:20505:53)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:20377:26)

at ProfilingCache_ProfilingCache.getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:20951:11)

at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:35462:33)

at Rh (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:13245:7)

at Ci (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:13944:7)

at uk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16725:86)

at tk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16245:11)

at qk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16237:23)

at jk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16221:5)

Component stack: at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:35445:34)

at div

at div

at div

at SettingsModalContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29121:3)

at Profiler_Profiler (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37243:34)

at ErrorBoundary_ErrorBoundary (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:30035:5)

at PortaledContent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:30157:5)

at div

at div

at ProfilerContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:34264:3)

at TreeContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25356:3)

at SettingsContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25963:3)

at ModalDialogContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:30300:3)

at DevTools_DevTools (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37639:3)

Issue 2:
With eslint-plugin-react-hooks@4.0.0 I observe an unexpected warning (with a weird behaviour) on custom hook call-site.

Steps To Reproduce

yarn create react-app hooks-bug

cd hooks-bug

npm run eject

npm i eslint-plugin-react-hooks@4.0.0

place code from the examples below into App.js

run npx eslint src/App.js

check output for warnings mentioned below

Code example:

function App(props) {
useSomeEffect(props, {});
return null;
}

function useSomeEffect() {}

export default App;

npx eslint src/App.js

./src/App.js

2:3 warning React Hook useSomeEffect has a missing dependency: 'props'. Either include it or remove the dependency array react-hooks/exhaustive-deps

✖ 1 problem (0 errors, 1 warning)

function App(props) {
useSomeEefect(props, {});
return null;
}

function useSomeEefect() {}

export default App;

npx eslint src/App.js

{no output}

The current behavior

react-hooks/exhaustive-deps warning triggered on a custom hook call-site

change to the hook name (so it doesn't contain the Effect part) fixes the warning

The expected behavior

react-hooks/exhaustive-deps should only be triggered on a custom hook definition-site (at least as far as I understand it)

change to the hook name should not affect the warning