Fix Failed to execute 'measure' on 'Performance' error

[unstubbable]

When startTime still has its initial value of -1.1 we must not call logComponentMount. This can occur when rendering a 'next/dynamic' component with {ssr: false} in a client component, for example. Unfortunately, I didn't manage to reproduce this scenario in a unit test.

[acdlite]

I believe you

[react-sizebot]

Comparing: 6a7650c...05a98de

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.js	=	6.68 kB	6.68 kB	=	1.83 kB	1.83 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	=	516.15 kB	516.15 kB	=	91.87 kB	91.87 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.69 kB	6.69 kB	=	1.83 kB	1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	619.52 kB	619.52 kB	=	109.51 kB	109.51 kB
facebook-www/ReactDOM-prod.classic.js	=	650.76 kB	650.76 kB	=	114.94 kB	114.94 kB
facebook-www/ReactDOM-prod.modern.js	=	641.04 kB	641.04 kB	=	113.38 kB	113.38 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 05a98de

[sebmarkbage]

This has a pair for offscreen too. You probably want to update that one as well. Usually these things come in twos. Offscreen/Regular or Mount/Unmount.

react/packages/react-reconciler/src/ReactFiberCommitWork.js

Line 3759 in 6a7650c

if (endTime - startTime > 0.05) {

It seems unexpected though because we always call startProfilerTimer in the work loop:

https://github.com/facebook/react/blob/main/packages/react-reconciler/src/ReactFiberWorkLoop.js#L2800-L2801

So how do we end up with a new Fiber that hasn't had its beginWork called yet we're visiting it in the passive mount phase?

Seems like there's something deeper going on here that's worth looking into.