[React 18] Possible Suspense Bug - Thrown error causes corrupted page

I've found what I think to be a React bug, although it could be something we are doing wrong inside Blitz.js `React 18.0.0-alpha-ed6c091fe-20210701` ## Basic Explanation The position of a top level, unneeded `<Suspense>` component next to an `<ErrorBoundary>` causes odd UI rendering or totally corrupted page. Following are different variations of [this code](https://github.com/flybayer/blitz-react18/blob/main/app/pages/_app.tsx#L15-L22) inside `_app.tsx` (which is the same top level root as Next.js) This code in `_app.tsx` causes a totally corrupted page (shows content on page that's no longer managed by React): ```tsx <Suspense fallback="Loading..."> <ErrorBoundary FallbackComponent={RootErrorFallback}> <Component {...pageProps} /> </ErrorBoundary> </Suspense> ``` This code in `_app.tsx` results in a correct end-result but has janky page transition. ```tsx <ErrorBoundary FallbackComponent={RootErrorFallback}> <Suspense fallback="Loading..."> <Component {...pageProps} /> </Suspense> </ErrorBoundary> ``` This code in `_app.tsx` without `<Suspense>` works flawless. ```tsx <ErrorBoundary FallbackComponent={RootErrorFallback}> <Component {...pageProps} /> </ErrorBoundary> ``` I feel like this is a React bug because, to my knowledge, position of a `<Suspense>` component should have zero affect on a thrown error or ErrorBoundary. ## Further Explanation In Blitz.js, we have a feature for restricting access to certain pages based on the user login status. We implement this [by throwing a custom `RedirectError`](https://github.com/blitz-js/blitz/blob/canary/packages/core/src/auth/auth-client.ts#L68-L74). And then inside our `<ErrorBoundary>` component, [we call `router.push()`](https://github.com/blitz-js/blitz/blob/canary/packages/core/src/error-boundary.tsx#L94-L98) when RedirectError is caught. And while the ErrorBoundary is in that temporary in-between state, we [render null](https://github.com/blitz-j…