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

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?