[Troubleshooting Postmortem] Chrome lag wasn’t due to low memory: Cloudflare Challenge retry loop caused high CPU (AIYA user repost)

General
, ,
1

Background

This troubleshooting targets a situation on Windows where Chrome is noticeably laggy, but system memory is not maxed out.

Observed symptoms:

  • Browser interactions feel sluggish; input latency is obvious
  • Task Manager shows memory headroom
  • Chrome CPU usage suddenly spikes

Troubleshooting steps (without closing tabs first)

  1. Continuously sample chrome.exe child processes and compute each PID’s CPU peak/average
  2. In Chrome Task Manager (Shift+Esc), sort by CPU and show PID
  3. Match the sampled system PIDs one-by-one to Chrome task entries

Key evidence

  • Within a 120-second window, Chrome total CPU peak was about 39.30%
  • Suspicious high-usage PIDs: 6952, 42292, 4956
  • In Chrome Task Manager:
    • PID 6952 = Subframe: https://challenges.cloudflare.com/
    • PID 42292 = Subframe: https://challenges.cloudflare.com/
  • PID 6952 peaked at 81.8% CPU
  • An extension process (Tampermonkey Beta) also showed high memory usage, which may amplify the Challenge retry issue

Conclusion

The core of this kind of lag is not memory, but repeated retries by Cloudflare Challenge subframes:

  • Verification scripts keep running (JS/WASM)
  • When multiple subframes run concurrently, CPU usage stacks and contends
  • The page becomes noticeably laggy

Why CF can be “continuously triggered”

Common causes:

  • After a long-idle tab resumes, the challenge token/cookie has expired
  • Proxy egress changes, and Cloudflare considers the session discontinuous
  • Cookie/local storage policies block state write-back
  • User scripts/extensions injections interfere with the challenge iframe
  • Multiple tabs on the same site trigger verification concurrently; failures and retries stack on each other

Actual result

After closing the relevant high-load pages, browser smoothness immediately returned, confirming the attribution.

Quick self-check for similar issues

  1. Press Shift+Esc to open Chrome Task Manager, sort by CPU, and show PID
  2. First check whether any challenges.cloudflare.com subframes are using CPU abnormally
  3. Temporarily disable user-script extensions on the target site and observe again
  4. Check proxy rules; if needed, let *.cloudflare.com go direct as a comparison
  5. Confirm that Cookie/site data policies are not blocking persistence of verification state