### Describe what you were doing when the bug occurred:
1. I did profiling on a list, that gets updated on each pagination api call.
2. Once the profiling was done, I moved around in the Profiler to view the Flamegraph
3. Moving to second capture, the Profiler crashed.


**DevTools version**: 4.6.0-6cceaeb67

```
Component stack: in ec
    in div
    in div
    in div
    in So
    in Unknown
    in n
    in Unknown
    in div
    in div
    in rl
    in Ze
    in fn
    in Ga
    in _s
```
fibersWithChangedErrorOrWarningCounts.add(fiberID);
     
    const fiberMap = type === 'error' ? fiberToErrorsMap : fiberToWarningsMap;
    const messageMap = fiberMap.get(fiberID);
    if (messageMap != null) {
      const count = messageMap.get(message) || 0;
      messageMap.set(message, count + 1);
    } else {
      fiberMap.set(fiberID, new Map([[message, 1]]));
    }
     
    updateMostRecentlyInspectedElementIfNecessary(fiberID);
     
     
     
     
     
     
    flushPendingErrorsAndWarningsAfterDelay();
  }
   
   
   
  
   
  if (process.env.NODE_ENV !== 'test') {
    registerRendererWithConsole(renderer, onErrorOrWarning);