<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

Repro steps using confidential internal fb tool provided separately (https://fb.workplace.com/groups/2299331103613797/permalink/2605716262975278/)

Gist of the repro:
1) open app
2) open react dev tools to profiling tab
3) turn on "Record why each component rendered while profiling"
4) interact with app
5) following error occurs: "TypeError: Cannot read property 'memoizedState' of null"
6) inspecting the flamegraph now shows incomplete information

Based on the stack trace, it looks like the issue occurs specifically on this line:
https://github.com/facebook/react/blob/3e94bce765d355d74f6a60feb4addb6d196e3482/packages/react-devtools-shared/src/backend/console.js#L135
console.warn(
            `Invalid component filter type "${componentFilter.type}"`,
          );
          break;
      }
    });
  }
   The renderer interface can't read saved component filters directly,
   because they are stored in localStorage within the context of the extension.
   Instead it relies on the extension to pass filters through.
  if (window.__REACT_DEVTOOLS_COMPONENT_FILTERS__ != null) {
    applyComponentFilters(window.__REACT_DEVTOOLS_COMPONENT_FILTERS__);
  } else {
    
    
    
    
     F
    applyComponentFilters(getDefaultComponentFilters());
  }
   If necessary, we can revisit optimizing this operation.
   For example, we could add a new recursive unmount tree operation.
   The unmount operations are already significantly smaller than mount opreations though.
   This is something to keep in mind for later.
  function updateComponentFilters(componentFilters: Array<ComponentFilter>) {
    if (isProfiling) {
       R
       I
      throw Error('Cannot modify filter preferences while profiling');
    }