wox-cpu-debug

Measure and attribute CPU hotspots in the Wox Go launcher without memory regressions.

27.3k|2.4k|Updated Dec 19, 2013

Search Tags:#CPU profiling #Performance Debugging #wox launcher #hotspot attribution #memory guardrail #process sampling #go pprof

One-click install

npx skills add https://github.com/Wox-launcher/Wox --skill wox-cpu-debug

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: wox-cpu-debug
Source: https://github.com/Wox-launcher/Wox/tree/main/.agents/skills/wox-cpu-debug
Command: npx skills add https://github.com/Wox-launcher/Wox --skill wox-cpu-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnosing CPU regressions in the Wox launcher is hard because Go pprof data, native renderer activity, and background work after hide can each distort the picture. This Skill provides a deterministic, repeatable workflow to measure query-active and hidden CPU in the real single-process Wox debug build and attribute hotspots to the correct owner.

Core Features & Use Cases

Deterministic workload replay: Drives the real Wox debug build through wox_automation with seeded mixed or fixed queries, keeping warm-up, profiling, and sampling in separate identical runs.
Cross-platform CPU sampling: Captures Go runtime/pprof profiles, macOS top/sample process data, and Windows TotalProcessorTime deltas or ETW stacks, with rules for handling Windows blocked-call profiling artifacts.
Memory guardrails: Requires before/after process footprint and Go retained-heap comparisons so CPU optimizations never trade for unbounded caches or retained native resources.
Use Case: When Wox shows high idle CPU after being hidden, run the hidden workload, sample the settled process for 30 seconds, capture native stacks, and classify whether a recurring timer, animation, or renderer stack is a real regression.

Quick Start

Use the wox-cpu-debug skill to measure Wox's hidden CPU usage on this machine and tell me whether any background work continues after the launcher is hidden.

Frequently Asked Questions about wox-cpu-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I optimize CPU without increasing memory usage?▼

Eliminate duplicate work, coalesce invalidations, and stop unnecessary scheduling rather than adding caches. Give any new cache or buffer a hard bound and release path, and compare warmed before/after process footprint, treating increases above 10 MiB or 5 percent as material.