Hi,
Thanks for contacting us.
Your description aligns with what appears to be a memory or resource leak behavior—where Resource Monitor becomes progressively less responsive and consumes more CPU, especially on systems with limited resources. The fact that restarting the tool immediately resolves the issue further supports this.
Summary of Observations
- Resource Monitor’s CPU graph shows escalating usage over time.
The perfmon.exe process under-reports its own usage in the task list.
Restarting Resource Monitor resets the graph and restores performance.
Behavior is consistent across systems, though severity varies by hardware.
Is This a Known Issue?
As of now, this specific behavior does not appear to be widely documented in official Microsoft channels or known issue lists for Windows. While there have been past reports of Resource Monitor performance degradation, your findings suggest a reproducible pattern that may warrant further investigation.
Recommended Next Steps
- File a Bug Report
- If you have access to Microsoft’s feedback or developer channels (e.g., via Feedback Hub or Partner Portal), I recommend submitting a bug report with:
- System specs
- Windows version/build
- Steps to reproduce
- Screenshots or logs showing CPU usage over time
- Temporary Workaround
- Until resolved, consider using Task Manager or Performance Monitor (perfmon.msc) directly for long-term monitoring, as they tend to be more stable.
- Monitor with Logging
- You can use
perfmon.mscto log Resource Monitor’s own performance counters over time to validate the leak and provide evidence for escalation.
- You can use
Let me know if you’d like help drafting the bug report or collecting diagnostic data. I’d be happy to assist.
Best regards,
Quinnie Quoc.