Memory leak in Query Monitor UI - GPCC 7.x and 6.x becomes unresponsive after prolonged use
search cancel

Memory leak in Query Monitor UI - GPCC 7.x and 6.x becomes unresponsive after prolonged use

book

Article ID: 402599

calendar_today

Updated On:

Products

VMware Tanzu Greenplum VMware Tanzu Greenplum / Gemfire VMware Tanzu Data Suite VMware Tanzu Data Suite

Issue/Introduction

Users may experience excessive memory consumption and eventual unresponsiveness when using the Query Monitor view in the Greenplum Command Center (GPCC) WebUI. The issue is consistently reproducible across different browsers.

Below are the symptoms of this issue:

  • Browser memory usage grows continuously while the Query Monitor tab is open (~300 MB every 5–10 minutes).

  • At ~8 to 13 GB RAM consumption, the UI becomes unresponsive and navigation to other tabs (e.g., Recommendations, Cluster Metrics) fails.

  • Query updates stop reflecting in real time.

  • Closing the GPCC tab immediately frees memory, confirming it is a frontend memory leak.

  • Occurs across multiple users and systems with no local browser extensions or changes.

 

Some example images shown below which shows that issue:

Cause

A memory leak in the Clarity core component was identified as the primary cause.

Resolution

The Clarity core component has been fixed.

As of August 2025, the current releases of GPCC have the memory leak. The fix will be released in the future releases of GPCC 6.x and 7.x

Monitor the Release Notes for the release of the fix.