Docs issue report from "getting-started/setup/editor-lifecycle.html"

[sarah123456l]

Origin URL

https://ckeditor.com/docs/ckeditor5/latest/getting-started/setup/editor-lifecycle.html

Project version

41.0.0

Is the information outdated? How?

No response

Is there something missing in the guide? What is it?

No response

Is there anything else you would like to add?

Eventhough editor.destroy() is called when i console.log the editor instance it still exist (its state is "destroyed")
I would expect it to be null
I also noticed there are detached elements related to ckeditor in memory heap snapshot of chrome devtool
and that can cause memory leaks..
(i have many instances of ckeditor in my app), i want them to be fully destroyed

Actually i am using the ckeditor5-angular lib, but the issue is reproducible with and without the ckeditor5-angular lib.

User agent

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36