Upcoming: Crash Log Viewer in Settings

[binaricat]

Crash Log Viewer — Coming Soon

We are adding a built-in Crash Log feature to help diagnose unexpected app behavior (like the issue reported in #452 where closing one SSH session closed the entire app).

What it does

Netcatty will now automatically capture main-process errors and write them to local log files. You can view them directly in Settings > System > Crash Logs.

What gets captured

Event	Description
uncaughtException	Unhandled errors in the main process
unhandledRejection	Unhandled Promise rejections
render-process-gone	Renderer crashes (OOM, killed, etc.)

What each log entry contains

• Error details: message, stack trace, error code (ECONNRESET, etc.), syscall, hostname/port
• Environment: app version, Electron version, OS version, platform/arch
• Runtime state: active session count, memory usage (RSS), process uptime, PID

How to use it

1. If the app crashes or behaves unexpectedly, reopen it
2. Go to Settings > System > Crash Logs
3. Expand a log entry to see full details
4. When reporting a bug, paste the crash log — it gives us everything we need to diagnose the issue

Additional details

• Logs are stored as JSONL files in userData/crash-logs/
• Auto-rotation: logs older than 30 days are automatically pruned
• You can clear all logs or open the log directory from the UI
• Benign errors (like EPIPE stream teardown) are filtered out to keep logs clean
• Large log files are efficiently tail-read to avoid performance issues

For bug reporters

Next time you encounter a crash, the crash log will tell us exactly what happened. No more guessing! Just paste the log entry in your issue and we can pinpoint the root cause.

Tracking PR: #454