Using untoggledComponent with MemoryAdapter in a vitest unit test causes OOM from re-render loop

[ghost]

Describe the bug
Using the untoggledComponent prop of the ToggleFeature component with MemoryAdapter appears to cause an infinite re-render loop resulting in an OOM Error in a vitest unit test.

We are using MemoryAdapter with a set of defaultFlags to provide "mock flags" to the unit tests, through a "mock" ConfigureFlopFilp provider.

To Reproduce
Steps to reproduce the behavior:

1. Given a ConfigureFlopFilp provider using MemoryAdapter and a set of defaultFlags,
2. Then when using the untoggledComponent prop of the ToggleFeature component such that we return a component from the toggledComponent prop, and return () => null from the untoggledComponent prop,
3. That causes an infinite re-render loop during a run of unit tests with vitest, and eventually exits with an OOM Error.
4. While using the same ToggleFeature in normal execution outside of test operates as expected.

Expected behavior
We should be able to use the same ToggleFeature with an untoggledComponent and a null/empty toggledComponent in the normal application and in a mocked unit test with the same result, and no infinite re-render/OOM.

Screenshots

Additional context
Replacing the ToggleFeature using untoggledComponent and a null/empty toggledComponent, with the use of the useFeatureToggle(flagName) hook and a conditional render of the untoggled component ovoids this OOM error. So it appears that there's some difference of behavior between the hook and the ToggleFeature component.

[tdeekens]

Thanks for reporting this issue in great detail. I'll try to make room to investigate it. If you find out more and can even propose a fix please don't hesitate to do so.