check-log

Analyze Firefox log files to diagnose media, EME, CDM, and GPU crash issues.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill check-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-log
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/check-log
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill check-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a Firefox log file for problems. Specializes in media/EME/CDM issues (hardware context reset, process crashes, HRESULT errors, PlayReady/CDM failures). Extensible to other Firefox subsystems.

Core Features & Use Cases

  • Analyze Firefox logs to detect hardware context resets and CDM/EME failures.
  • Correlate signals such as MF_MEDIA_ENGINE_EVENT_ERROR, HRESULT codes, device loss, and IPC errors.
  • Load relevant knowledge files to interpret signals and produce a structured report.

Quick Start

Provide the path to a Firefox log file for analysis.

Frequently Asked Questions about check-log

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

FAQPage Schema
How do I diagnose Firefox media and GPU crashes from a log file?

To diagnose Firefox log issues, provide a log file path for analysis. The tool extracts media, EME, CDM, and GPU events, cross-references knowledge files, and outputs a structured timeline of crash diagnostics.

What is causing hardware context resets and CDM failures in my Firefox logs?

Hardware context resets and CDM failures in Firefox logs are caused by correlated signals like MF_MEDIA_ENGINE_EVENT_ERROR, HRESULT codes, and device loss. The tool interprets these signals to produce a structured findings report.

Can I analyze PlayReady and EME process crashes using Firefox crash diagnostics?

Yes, you can analyze PlayReady and EME process crashes using Firefox crash diagnostics. The tool validates log paths, reads multimedia component contexts, and detects IPC errors related to CDM failures.

How do I identify HRESULT errors and device loss events in Firefox multimedia logs?

To identify HRESULT errors and device loss in Firefox multimedia logs, the tool reads the file, extracts matching events, and correlates them with GPU driver contexts to output a structured diagnostic timeline.

Does this Firefox log analysis approach work for other browser subsystems beyond GPU and media?

The Firefox log analysis approach specializes in media, EME, CDM, and GPU subsystems but is extensible to other Firefox subsystems. It applies to logs from multimedia components and crash-diagnostic workflows.

What do I need to start troubleshooting Firefox EME and GPU driver issues?

To start troubleshooting Firefox EME and GPU driver issues, you only need to provide the path to a Firefox log file. The tool handles path validation, event extraction, and report generation automatically.