Diagnose frozen Emacs processes by sampling stacks and analyzing root causes.
npx skills add https://github.com/benthamite/dotfiles --skill emacs-freeze
Please help me install this Agent Skill. Skill: emacs-freeze Source: https://github.com/benthamite/dotfiles/tree/main/claude/skills/emacs-freeze Command: npx skills add https://github.com/benthamite/dotfiles --skill emacs-freeze
This Skill helps diagnose and resolve situations where Emacs becomes unresponsive or frozen, preventing data loss and restoring productivity.
C-g does not respond, use this Skill to understand why and how to safely exit or fix the issue.Diagnose why Emacs is frozen by running the emacs-freeze skill.
High-intent search queries and answers about installing and using this skill.
To diagnose an unresponsive Emacs instance, you can sample the process to analyze stack traces, process statistics, and open files to identify the root cause of the freeze. This approach pinpoints issues like infinite recursion, I/O blocking, or garbage collection pressure.
Emacs freezes are typically caused by infinite recursion, I/O blocking, or excessive garbage collection pressure. Analyzing stack samples and process statistics helps identify these underlying issues when the editor becomes unresponsive and standard cancellation fails.
Troubleshoot a frozen Emacs process by using system utilities like pgrep, ps, sample, lsof, and wc to collect diagnostic data. These tools gather stack samples, process statistics, open files, and thread counts for root cause analysis.
Yes, analyzing Emacs stack traces requires system utilities like pgrep, ps, sample, lsof, and wc for diagnostics. These tools are necessary to pinpoint the frozen process and collect essential system information for root cause analysis.
The best way to recover from an Emacs hang is to analyze collected diagnostic data to identify the root cause, then apply actionable steps for immediate recovery. This process also suggests measures to prevent future occurrences of unresponsiveness.
Yes, you can identify the root cause of an Emacs freeze without terminating by sampling the process and analyzing stack traces. This diagnostic data collection identifies issues like infinite recursion or I/O waits while preserving the session.
kunwl123456List and terminate system processes with pattern-based safety checks.
agwacomDelete the freeze state file to restore editing across all directories.
jingtaozfAutomate Emacs Lisp debugging with edebug, tracing, and profiling workflows.
Mithrandir21Analyze Android ANR trace logs to identify thread blocking and contention issues.