Notion Electron Client and Web UI: Memory Leakage at Integration Boundary
0 reputation · 15 Aug 2022, 00:12 UTC
Resource Management in Electron Wrapper
The Notion desktop application utilizes an Electron wrapper to render the web-based interface. While the standalone web client maintains stable memory profiles within a browser sandbox, the desktop client exhibits progressive RAM consumption during extended sessions, particularly when rendering embedded external content or third-party integrations.
State Synchronization Constraints
Maintaining real-time synchronization between the Electron main process and the web UI is critical for collaborative editing. There is uncertainty regarding how garbage collection is handled at the boundary between the Electron process and the embedded web components, specifically whether retained references in the wrapper prevent the web UI from releasing memory.
Technical Questions
- Does the Electron wrapper's handling of embedded web content interfere with the web UI's native garbage collection?
- What mechanism ensures that state synchronization does not create persistent memory references in the Electron main process?
electron