LOW
The severity is rated as LOW because this issue affects user experience rather than system security. The problem does not present a direct risk to data confidentiality, integrity, or availability but can cause significant inconvenience during long coding sessions.

The issue described pertains to the performance degradation experienced when using ChatGPT for extensive coding sessions in a web browser. As the number of chat messages increases, the browser struggles with rendering each message as a DOM element, leading to significant lag and high CPU usage. The root cause is not related to the API but rather the browser's handling of a large volume of dynamic content. A proposed solution involves a Chrome extension that optimizes the display by limiting the number of messages rendered at once, which significantly improves usability without deleting any chat history.

Affected Systems
  • Google Chrome
  • ChatGPT web interface
Affected Versions: All versions of Google Chrome and ChatGPT's web interface that do not implement message rendering optimization
Remediation
  • Install the proposed Chrome extension from a trusted source to limit DOM element rendering.
  • Monitor browser performance using Developer Tools (F12) to identify high CPU usage patterns related to DOM manipulation.
  • Consider pinning the ChatGPT web interface version that includes message rendering optimization, if available.
Stack Impact

This issue has minimal direct impact on common homelab stacks but can affect developers using Chrome for coding sessions with ChatGPT. The primary concern is browser performance degradation when handling extensive chat logs.

Source →