Bug: Render after suspense is thrown away leaving DOM unmatched with state

[joeljeske]

React version: 16.12.0

Steps To Reproduce

A component that suspends as a result of a context update is never rendered to DOM after suspension is finished.

Link to code example:

https://codesandbox.io/s/react-suspense-context-bug-rklls?file=/package.json:163-170

The current behavior

If a component suspends as a result of a context update, the component's render is called after suspension is finished but the result of the render is not reflected in the DOM (and effects aren't called).

The expected behavior

If a component suspends as a result of a context update, the component's render should be called and flushed to the DOM and effects called.

Related Issues:

#17356 - seems related to memoization but this does not use any memoization

[chriserickson-cb]

We ran into this same problem, the codesandbox seems like a pretty good reproduction case.

We're on React 16.9 / React Native 0.61.5.

[gaearon]

I think this is a duplicate of #17356.

seems related to memoization but this does not use any memoization

It does use memoization in the sense that children is always going to be the same element since it's passed from above.