### Website or app

https://github.com/eps1lon/react-devtools-repro-no-matching-node/

### Repro steps

1. `yarn start`
2. Open `App.js`
3. Uncomment the `useEffect` block
4. Click to inspect "Component" in DevTools
5. Error: "_Could not inspect element with id 5_"

Originally reported in https://github.com/facebook/react/issues/21436#issuecomment-835406075

---

https://user-images.githubusercontent.com/12292047/117544707-e6a6cd80-b022-11eb-9f8f-bb8cfd9f7743.mp4

### How often does this bug happen?

Every time

trackedPathMatchDepth++;
         Are 
        if (trackedPathMatchDepth === trackedPath.length - 1) {
           The
           Don
          mightBeOnTrackedPath = false;
        } else {
           Che
          mightBeOnTrackedPath = true;
        }
         In 
         to 
        return false;
      }
    }
     This Fiber's parent is on the path, but this Fiber itself isn't.
     There's no need to check its children--they won't be on the path either.
    mightBeOnTrackedPath = false;
     However, one of its siblings may be on the path so keep searching.
    return true;
  }
  function updateTrackedPathStateAfterMount(mightSiblingsBeOnTrackedPath) {
     updateTrackedPathStateBeforeMount() told us whether to match siblings.
     Now that we're entering siblings, let's use that information.
    mightBeOnTrackedPath = mightSiblingsBeOnTrackedPath;
  }
   Roots don't have a real persistent identity.
   A root's "pseudo key" is "childDisplayName:indexWithThatName".
   For example, "App:0" or, in case of similar roots, "Story:0", "Story:1", etc.
   We will use this to try to disambiguate roots when restoring selection between reloads.