top-crashers

Query Brave's Backtrace crash reporting system to identify and analyze top crashers.

3.5k|1.4k|Updated Nov 10, 2017

Search Tags:#debugging #stability #regression #backtrace #crash analysis #brave browser

Ready to run

npx skills add https://github.com/brave/brave-core --skill top-crashers-brave

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: top-crashers
Source: https://github.com/brave/brave-core/tree/main/.claude/skills/top-crashers
Command: npx skills add https://github.com/brave/brave-core --skill top-crashers-brave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly identify and understand the most frequent crashes occurring in the Brave browser, enabling faster bug fixing and stability improvements.

Core Features & Use Cases

Identify Top Crashers: Get a ranked list of crash signatures, their frequency, and affected platforms/versions.
Analyze Crash Details: View stack traces, code origin (Brave vs. Chromium), and regression indicators.
Prioritize Fixes: Focus on crashes impacting users most, especially those in current development branches (Nightly).
Use Case: A developer can ask "What are the top 5 crashers on Nightly this week?" to immediately see the most critical stability issues they need to address.

Quick Start

Use the top-crashers skill to list the top 10 crashers in the last 7 days.

Frequently Asked Questions about top-crashers

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

FAQPage Schema

How do I identify the top crashers in the Brave browser?▼

Analyze Brave browser crashes by querying the Backtrace system to retrieve detailed crash signatures, stack traces, and platform breakdowns. It classifies code origin to distinguish Brave vs. Chromium regressions for targeted debugging.

How do I analyze Brave browser stack traces for regression detection?▼

Can I filter Brave crash analysis by platform, version, and channel?▼

Yes, crash analysis supports filtering by days, platform, version, channel, and code origin. This isolates specific stability issues affecting distinct environments like the Nightly development branch for focused debugging.

Does the crash analysis distinguish between Brave and Chromium code origin?▼

Yes, the analysis classifies code origin to distinguish between Brave and Chromium. This helps developers determine whether to fix the bug internally or report an upstream Chromium issue.

What is the best way to prioritize Brave browser stability fixes?▼

Prioritize stability fixes by ranking crash signatures by frequency and focusing on those impacting current development branches. Identifying top crashers helps developers address the most critical user-facing issues first.

Can I get machine-parseable output for Brave crash signatures?▼

Yes, Brave crash analysis outputs results in both human-readable and machine-parseable formats. This allows developers to integrate crash signatures and stack traces directly into automated debugging workflows.