<!--
  Note: if the issue is about documentation or the website, please file it at:
  https://github.com/reactjs/reactjs.org/issues/new
-->

**Do you want to request a *feature* or report a *bug*?**

A bug.

**What is the current behavior?**

componentDidCatch isn't called when a child component renders a void element containing another element. The app just crashes.
If it contains just text, the same error ("...is a void element tag and must neither have children nor use dangerouslySetInnerHTML") appears, but this time with componentDidCatch properly called.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**

https://codesandbox.io/s/0042z5wrlp
The behavior is different when you change Comp1 with Comp2.

**What is the expected behavior?**

componentDidCatch should be called in both cases.

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**

16.5.2. 
In 16.4.2 it worked correctly.
let prevInteractions: Set<Interaction> = (null: any);
  if (enableSchedulerTracing) {
    
    
    prevInteractions = __interactionsRef.current;
    __interactionsRef.current = root.memoizedInteractions;
  }
  
  ReactCurrentOwner.current = null;
  let firstEffect;
  if (finishedWork.effectTag > PerformedWork) {
    
    
    
    
    if (finishedWork.lastEffect !== null) {
      finishedWork.lastEffect.nextEffect = finishedWork;
      firstEffect = finishedWork.firstEffect;
    } else {
      firstEffect = finishedWork;
    }
  } else {
    
    firstEffect = finishedWork.firstEffect;
  }
  prepareForCommit(root.containerInfo);
  
  nextEffect = firstEffect;
  startCommitSnapshotEffectsTimer();
  while (nextEffect !== null) {