cpu-profile-analysis

What problem does it solve? Raw .cpuprofile and DevTools Trace-*.json files are massive, single-line JSON blobs that are nearly impossible to inspect manually, making it hard to find slow functions, long tasks, or rendering bottlenecks in VS Code and Electron apps. ## Core Features & Use Cases - CPU Profile Analysis: Parse V8 sampling profiler data to compute self-time per function, identify activity regions, and measure timing between milestones. - DevTools Trace Analysis: Extract user timing marks, long tasks, layout/paint events, GC pressure, and input latency from Chrome Trace Event Format files across Renderer, Browser, and GPU processes. - Huge File Handling: Buffer-based parsing for files exceeding V8's ~512MB string limit, with embedded ProfileChunk reconstruction. - Use Case: Given a 200MB Trace-*.json from a slow VS Code session, identify which functions blocked the main thread, when code/didResolveTextFileEditorModel fired, and how much time GC consumed. ## Quick Start Analyze the attached Trace-2024.json file and tell me which functions consumed the most CPU time on the renderer main thread.