Notion Electron Client and Web UI: Memory Leakage at Integration Boundary

Analysis of Memory Leakage

The Electron wrapper can interfere with the web UI's native garbage collection if the main process retains active references to BrowserWindow or webContents objects. There is no native Electron mechanism that automatically prevents state synchronization from creating persistent memory references; memory management at the IPC boundary must be handled explicitly by the application developer.

Established Behavior vs. Likely Cause

Established Electron Behavior: A BrowserWindow typically disposes of its webContents only when the window is closed. Navigating to a different URL or replacing embedded content within a session does not automatically destroy the renderer context or clear the associated heap. If the main process stores a reference to a window in a global variable or registers an ipcMain listener without a corresponding removal, the renderer's memory may remain reachable from the main process, blocking garbage collection (GC).

Likely Explanation (Pending Verification): The progressive RAM growth observed during the rendering of embedded external content suggests a leak at the integration boundary. This often occurs when webview elements or iframes are used; if the main process maintains a handle to these elements or their webContents, the memory allocated for that embedded session cannot be reclaimed. Additionally, third-party integration scripts may create closures that hold references to the renderer's global object, preventing the browser sandbox from releasing memory even if the Electron wrapper attempts a cleanup.

Verification and Scoped Diagnostics

To determine if the main process is blocking the renderer's GC, the following verification steps are recommended:

• Main Process Heap Audit: Attach a debugger to the main process (using --inspect) and use the Memory tab to check for multiple BrowserWindow or webContents instances that persist after the corresponding UI elements have been closed or navigated away from.
• Renderer Profiling: Use the Chrome DevTools attached to the renderer process to take heap snapshots before and after loading an embedded integration. If objects from the integration persist after it is removed from the DOM, a reference is being held.
• Listener Audit: Review the main process code for ipcMain.on or webContents.on calls that lack a corresponding .removeListener() call during the window's closed or destroyed events.

Required Diagnostic Detail

To refine this recommendation, please specify whether the embedded external content is implemented via <webview> tags or standard <iframe> elements. This distinction is critical because <webview> runs in a separate process with its own webContents managed by the main process, whereas iframes are managed within the renderer's own memory space.