How to troubleshoot Binance Mac crashes? Where are the log files?

Binance Mac client logs are primarily located in three places: 1. ~/Library/Application Support/Binance/logs/ for application runtime logs; 2. ~/Library/Logs/Binance/ for system-level logs; and 3. ~/Library/Logs/DiagnosticReports/ for crash reports. You can view them in real-time using Console.app or the log stream --predicate 'subsystem == "com.binance.app"' command. Troubleshooting also requires checking network logs and WebSocket status. Download the client from the Binance official website; mobile apps also have logs, which you can click Binance Official APP to download for comparison. This article covers log directories, Console usage, and typical errors in detail.

1. Where Exactly Are the Logs?

Application logs on Mac follow a fixed directory structure:

Path	Purpose	Readability
~/Library/Application Support/Binance/logs/	App Business Logs	High
~/Library/Logs/Binance/	System Integration Logs	Medium
~/Library/Caches/Binance/Cache/	Network Cache	Low
~/Library/Logs/DiagnosticReports/	Crash Reports	Medium
/var/log/system.log	Legacy System Logs	Medium
Console.app Real-time Stream	All Unified Logs	High

Quick access method: Finder → Command + Shift + G → Paste the path → Enter. Or via Terminal:

open ~/Library/Application\ Support/Binance/logs/

2. Business Logs under Application Support

1. Log Categories

~/Library/Application Support/Binance/logs/
├── main.log              # Main process
├── renderer.log          # Renderer process
├── network.log           # Network requests
├── websocket.log         # WebSocket market data push
├── trading.log           # Trading operation records
├── error.log             # Error summary
└── archive/              # Historical logs (7-day rotation)

2. Real-time Viewing

tail -f ~/Library/Application\ Support/Binance/logs/main.log

Or view all logs mixed:

tail -f ~/Library/Application\ Support/Binance/logs/*.log

3. Filtering by Time

grep "2026-04-15" ~/Library/Application\ Support/Binance/logs/network.log

4. Filtering by Keywords

grep -i "error\|fail\|timeout" ~/Library/Application\ Support/Binance/logs/*.log

3. Console.app

1. Opening

Spotlight search for Console.app, or go to Applications → Utilities → Console.

2. Filtering Binance Logs

Click "Your Device Name" in the sidebar → Type Binance in the top search box → Enter.

3. Saving Current Logs

Menu Bar: File → Export → Save as a .logarchive file, to be included when sending to technical support.

4. Viewing Crash Reports

Sidebar → Crash Reports:

• Lists all application crash records.
• Click an entry to view the full stack trace.
• Right-click → Show in Finder to jump to the .crash file location.

4. The log Command (Recommended for advanced users)

macOS comes with a powerful log command tool.

1. Real-time Stream

log stream --predicate 'subsystem CONTAINS "binance"' --style compact

2. Logs from the last 1 hour

log show --predicate 'subsystem CONTAINS "binance"' --last 1h

3. Filtering by Process Name

log show --predicate 'process == "Binance"' --last 30m

4. Exporting to a File

log show --predicate 'process == "Binance"' --last 4h > ~/binance-debug.log

5. Filtering Error Levels

log show --predicate 'process == "Binance" AND messageType == "error"' --last 24h

5. Crash Reports Detailed

1. Path

~/Library/Logs/DiagnosticReports/Binance-*.ips

Changed to .ips format since Sonoma (previously .crash), which is essentially JSON.

2. Viewing Tools

• Console.app automatically parses them.
• Open directly with a text editor.
• Command line:

ls -lt ~/Library/Logs/DiagnosticReports/Binance-* | head -5
cat ~/Library/Logs/DiagnosticReports/Binance-2026-04-15-*.ips | jq .

3. Key Fields

Field	Meaning
cpuType	CPU architecture at crash (arm64/x86_64)
osVersion	macOS version number
bundleInfo.CFBundleShortVersionString	Binance version
exception.type	Exception type (EXC_BAD_ACCESS / SIGABRT)
threads	Stack traces of all threads at crash

4. Common Crash Causes

• EXC_BAD_ACCESS: Accessing a null pointer, often seen when old data remains after an update.
• SIGABRT: Active termination, usually when the Electron renderer process freezes.
• EXC_CRASH: Caused by abnormal API return values.
• Memory Pressure Crash: Indicated by the __vm_deallocate stack.

6. Typical Error Reference Table

Locate issues based on keywords in the logs:

Log Keyword	Issue	Solution
ECONNREFUSED	Connection refused	Check proxy/firewall
ETIMEDOUT	Connection timed out	Change DNS or proxy
certificate has expired	Certificate expired	Update system time
Invalid API key	API key error	Regenerate the key
timestamp for this request is outside	Time out of sync	Sync time via NTP
WebSocket closed: 1006	Abnormal closure	Check network stability
Keychain access denied	Keychain access denied	Reset keychain permissions
QuotaExceededError	Local storage full	Clear cache

7. Cleaning Logs and Cache

1. Cleaning Business Logs

rm -rf ~/Library/Application\ Support/Binance/logs/archive/

2. Cleaning Cache

rm -rf ~/Library/Caches/Binance/

3. Cleaning Crash Reports

rm ~/Library/Logs/DiagnosticReports/Binance-*

4. Resetting the Client

Complete reset:

killall Binance
rm -rf ~/Library/Application\ Support/Binance/
rm -rf ~/Library/Preferences/com.binance.app.plist
rm -rf ~/Library/Caches/Binance/

The next launch will be equivalent to a fresh install (requiring a new QR code login).

8. Enabling Client Debug Mode

1. Launch Parameters

Launch via Terminal with parameters:

/Applications/Binance.app/Contents/MacOS/Binance --debug --verbose

2. Environment Variables

export BINANCE_DEBUG=1
export ELECTRON_ENABLE_LOGGING=1
open /Applications/Binance.app

3. Electron DevTools

Press Command + Option + I to potentially open DevTools (supported in some versions) to view Network, Console, etc., similar to browser debugging.

9. What to Include in a Bug Report

When providing feedback to Binance official support, include:

1. macOS version: sw_vers;
2. Binance version: Client Settings → About;
3. Logs from the last 1 hour (exported as logarchive);
4. .ips crash report;
5. Reproduction steps and timestamps;
6. CPU architecture: uname -m.

You can package these all at once:

mkdir ~/binance-debug-report
cp -r ~/Library/Application\ Support/Binance/logs ~/binance-debug-report/
cp ~/Library/Logs/DiagnosticReports/Binance-*.ips ~/binance-debug-report/
sw_vers > ~/binance-debug-report/system.txt
uname -a >> ~/binance-debug-report/system.txt
tar -czf ~/binance-debug.tar.gz -C ~ binance-debug-report

Send the resulting binance-debug.tar.gz to technical support.

10. Network Layer Packet Capture

Deeper troubleshooting requires capturing packets to inspect requests:

1. Charles Proxy

• Install Charles (configure SSL certificates).
• Set Mac system proxy to Charles (127.0.0.1:8888).
• Launch Binance → Observe requests.
• Filter for the binance.com domain.

2. Wireshark

brew install --cask wireshark

Capture traffic on the entire network interface, suitable for analyzing TCP layer issues (e.g., RST, handshake failure).

3. mitmproxy (Command line)

brew install mitmproxy
mitmproxy --mode transparent --listen-port 8080

Lightweight packet capture.

FAQ

Q1: Log files are getting too large; how can I clean them automatically?

A: The client has a built-in 7-day rotation and deletes them automatically. For more aggressive cleaning, you can write a crontab entry:

0 2 * * * find ~/Library/Application\ Support/Binance/logs -mtime +3 -delete

This cleans logs older than 3 days at 2:00 AM every day.

Q2: Why can't I see any Binance logs in Console.app?

A: Ensure the search keyword correctly matches the subsystem; try com.binance or simply type Binance. Also, the client must be running for log output.

Q3: A lot of EACCES permission errors appear in the logs?

A: The client might be installed in /Applications/ (visible to all users), but the log directory may lack write permissions. Solution:

sudo chown -R $(whoami) ~/Library/Application\ Support/Binance

Q4: What if I can't understand the .ips crash report?

A: Send the file to Binance official technical support; they have symbol tables to restore readable function names. Your primary goal in viewing it is to get the timestamp and exception type.

Q5: Is my account information leaked in the logs?

A: Binance client logs record some API responses (including Account ID and assets) but do not record passwords or 2FA. Before sharing logs, it's best to anonymize them using sed 's/account_id=[0-9]*/account_id=***/g'.

For more troubleshooting tips, visit the Mac Guide category in the Categories.