claude-code - 💡(How to fix) Fix [BUG] Significant performance degradation after updating from 1.1.5749 to 1.1.7714 on Linux. [2 comments, 2 participants]

• Electron processes consume ~2.1 GB RAM on startup (fresh launch)
• Previous version (1.1.5749) was fluid with the same MCP server configuration
• UI freezes and goes white under normal usage
• Slowness persists even after disabling non-essential MCP servers

TL;DR

Downgrade to version 1.1.5749 or disable non-essential MCP servers to potentially mitigate the performance degradation and high memory usage in Claude Desktop 1.1.7714 on Linux.

Guidance

• The significant increase in memory usage and performance degradation after updating from 1.1.5749 to 1.1.7714 suggests a regression bug, potentially related to how the new version handles MCP servers or Electron processes.
• Disabling non-essential MCP servers, as attempted, showed partial improvement, indicating that the number of active servers might be a contributing factor to the issue.
• Switching to native Wayland mode also provided partial improvement, which could imply that there are rendering or display-related inefficiencies in the newer version.
• To further troubleshoot, try disabling all non-essential MCP servers and observe if the performance and memory usage return to expected levels, then re-enable servers one by one to identify if a specific server causes the issue.

Example

No specific code changes are suggested without more detailed information on the internal workings of Claude Desktop or the MCP server integrations. However, monitoring system resources and application logs while interacting with the application could provide more insights into what might be causing the slowdown.

Notes

The lack of error messages or logs limits the ability to pinpoint the exact cause. The issue seems to be related to the update and the configuration of MCP servers, but without more specific details on how these servers interact with Claude Desktop, it's challenging to provide a definitive fix.

Recommendation

Apply workaround: Downgrade to version 1.1.5749 if possible, as it is known to work as expected, until a fix for the regression in 1.1.7714 is available. This is recommended because downgrading is a straightforward way to immediately mitigate the performance issues and high memory usage, allowing for continued use of the application without the significant degradation experienced in the newer version.