### Website or app

Please checkout the linked branch not `main`
https://github.com/eps1lon/react-devtools-repro-no-matching-node/tree/repro/elements-leaking
Repro steps and screen recording included in the repro

### Repro steps

1. Clone repro
1. yarn
1. yarn start
1. Open app page
1. open devtools
1. Uncomment the `useEffect` block i.e. add an effect
1. inspect `Component` element
1. comment `useEffect` block i.e. remove the effect
1. Repeat comment/uncomment to see that children grow indefinitely


### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

Could not inspect element with id 4

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_

Might be a duplicate of https://github.com/facebook/react/issues/21436#issuecomment-835406075 since the repro steps are the same. But depending on what the effect is doing, the behavior is different.
ContextProvider: 12,
      CoroutineComponent: -1, 
      CoroutineHandlerPhase: -1, 
      DehydratedSuspenseComponent: -1, 
      ForwardRef: 13,
      Fragment: 9,
      FunctionComponent: 0,
      HostComponent: 7,
      HostPortal: 6,
      HostRoot: 5,
      HostText: 8,
      IncompleteClassComponent: -1, 
      IndeterminateComponent: 4,
      LazyComponent: -1, 
      LegacyHiddenComponent: -1,
      MemoComponent: -1, 
      Mode: 10,
      OffscreenComponent: -1, 
      Profiler: 15,
      ScopeComponent: -1, 
      SimpleMemoComponent: -1, 
      SuspenseComponent: 16,
      SuspenseListComponent: -1, 
      YieldComponent: -1, 
    };
  } else {
    ReactTypeOfWork = {
      CacheComponent: -1, 
      ClassComponent: 2,
      ContextConsumer: 12,