editor.load() cause memory leak!

[YousofSayed]

editor.load() causes memory leak

I'm using GrapesJS with @grapesjs/react.
When I call editor.load() multiple times, I notice a continuous increase in DOM nodes and memory usage in the browser's Performance Monitor.

• The DOM node count keeps increasing without ever decreasing.
• Even after calling editor.destroy(), the memory does not decrease, which strongly suggests a memory leak.

---

Steps to Reproduce

1. Initialize GrapesJS with @grapesjs/react.
2. Call editor.load() repeatedly while keeping the Performance Monitor open.
3. Observe:
   • DOM nodes keep increasing.
   • Memory usage keeps growing and never goes down.
4. Call editor.destroy() and check memory usage — it stays the same.

---

Expected Behavior

• Memory and DOM nodes should return to normal after destroying the editor.
• editor.load() should not accumulate detached DOM nodes or event listeners.

---

Actual Behavior

• Memory grows with every editor.load() call.
• Destroying the editor does not free up memory.

---

Environment

• GrapesJS version: (latest at time of testing)
• @grapesjs/react version: (latest at time of testing)
• Browser: Chrome (latest)
• OS: Windows 10

---

Notes

This issue makes it very difficult to use GrapesJS in a production React app because memory usage keeps increasing, eventually causing performance degradation or crashes.