Is DISABLE_COMMIT_PAUSING_MECHANISM (with the preventShadowTreeCommitExhaustion patch) safe for production?

[alexnaiman]

Hi, I'd like to check on the production-readiness of DISABLE_COMMIT_PAUSING_MECHANISM.

We're seeing scroll jitter on animated components with the New Architecture enabled, and the performance docs point to this flag (paired with preventShadowTreeCommitExhaustion on the React Native side) as the main fix.

The feature flags docs recommend enabling preventShadowTreeCommitExhaustion via a patch to ReactNativeFeatureFlagsDefaults.h and building React Native from source, rather than the full reactNativeReleaseLevel: experimental setting.

Questions:

1. Is this patch-based approach (without the experimental release level) considered stable enough for a production app, or is it still recommended only for early adopters/testing?
2. Are there known edge cases or side effects to watch for beyond what's already documented (e.g. app unresponsiveness if preventShadowTreeCommitExhaustion isn't properly enabled)?
3. Is this combination actively used in production by any apps you're aware of, or still mostly experimental in practice?

Thanks!