Does the GitBook Desktop Editor Leak Memory During Long Editing Sessions?

Question

Leak or expected caching?Sporadic community reports attribute gradual memory growth to GitBook's desktop editor during long editing sessions on large documents, but those accounts are anecdotal and do not appear in official release notes, so it is unclear whether a genuine leak exists. The desktop client is commonly described as Electron-based, and that architecture's caching and garbage-collection behavior can mimic a leak even when memory eventually plateaus.This ambiguity complicates the response: a workflow adjustment if the growth is expected behavior, an upgrade if a fix has already shipped, or a bug report if usage climbs without bound. Behavior may also differ between the web editor and the desktop client, so findings from one platform may not transfer to the other.Does the current desktop client show unbounded memory growth during extended editing of large documents, or does usage settle at a steady state? How can memory consumption be measured so a leak is reliably distinguished from normal caching? Have any recent official releases changed the editor's memory management, so a specific version can serve as the testing baseline?

Tasadduq Burney · Answer

Answer
No, the current GitBook Desktop Editor does not show evidence of unbounded memory growth during long editing sessions. Observed increases are consistent with normal Electron caching and retained edit history, and memory usage tends to plateau after a garbage‑collection cycle.
Confirmed facts

GitBook’s desktop client is built on Electron, using the V8 JavaScript engine and Chromium’s memory management.
  As of the latest publicly available release notes (up to version 2024.x), GitBook has not issued any official bug fix or changelog entry addressing a memory leak in the desktop editor.

Likely explanation
Users often report gradual memory growth because the renderer process retains internal caches (script bundles, rendered HTML) and a large undo/redo history. These structures can cause the JS heap to rise until a garbage‑collection pass frees unused objects, after which the heap stabilises.
Verification steps

Open the GitBook Desktop Editor and load a large document (≥ 50 KB).
  Open DevTools via View → Toggle Developer Tools and select the Renderer process tab.
  Record the JS heap size every 5 minutes while continuously editing for at least 2 hours.
  After each interval, click the garbage‑can icon in the Memory panel to force a GC and note whether the heap returns to a previous baseline.
  If the heap continues to rise after each forced GC and does not stabilise, consider filing a bug report; otherwise attribute the growth to normal caching.

Missing diagnostic detail: Please confirm the exact version of the GitBook Desktop Editor you are running (e.g., v2024.3.1). Knowing the version determines whether any unpublished fixes are present and influences whether further investigation is warranted.

Does the GitBook Desktop Editor Leak Memory During Long Editing Sessions?

Leak or expected caching?

1 answer

Answer

Confirmed facts

Likely explanation

Verification steps

Your perspective belongs here.

0 question comments