Bug: Detached node memory leak when using key and focus contenteditable element

[TUTOR03]

The DOM node stays in memory as a detached node if it has a content editable element inside what is focused using ref and that component is used with key prop in parent.

React version: 18.2.0, 17.0.2

Steps To Reproduce

All steps to reproduce are written in README file for this repo.
Also there is a source code to reproduce the bug.

The current behavior

The DOM node stays in memory as a detached node and can not be collected with garbage collector.

The expected behavior

The DOM node doesn't stay in memory as a detached node.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!

[VMBindraban]

I runned the performance profiler for a minute and while the JSHeap is being cleaned up the nodes keeps on rising.
The app repaints between the 1 and 3 seconds.