Dragonframe启动数秒后意外关闭，请求排查故障原因

Hey, let's figure out why your Dragonframe 3.6.1 is crashing right after launch. Based on the process details you shared and common issues with this app, here are the most probable causes and fixes:

1. Architecture Compatibility Issues #

Your Dragonframe is built as native X86-64 code. If you're running this on an Apple Silicon (M-series) Mac, even with Rosetta 2 translation, older app versions like 3.6.1 often hit compatibility snags that cause immediate crashes.

• Quick check & fix: Right-click Dragonframe.app → Get Info, then toggle the "Open using Rosetta" option. If it was already checked, uncheck it (some apps behave better without forced Rosetta) and try launching again.

2. Corrupted Preferences or Cache #

Over time, the app's preference files or cached data can get corrupted, making it fail to load properly on startup.

• Step-by-step fix:
  • Open Activity Monitor, search for "Dragonframe", and force quit any related processes.
  • Go to ~/Library/Preferences/, find com.dzed.Dragonframe.plist, make a backup, then delete it.
  • Navigate to ~/Library/Caches/com.dzed.Dragonframe/, delete the entire folder.
  • Restart Dragonframe—it'll generate fresh preference files automatically.

3. Damaged Installation #

The app package might have been corrupted during download or installation, leading to missing critical files.

• Fix:
  • Fully uninstall Dragonframe: Drag the app to Trash, then delete the preference and cache folders mentioned above.
  • Re-download the installer from the official Dragonframe website, then reinstall the app.

4. User Account Permissions or Corruption #

Your user ID is 501 (a standard admin account), but permission issues or a corrupted user folder could still cause the crash.

• Troubleshoot:
  • Log into a different admin account on your Mac, then try launching Dragonframe. If it works, the problem is tied to your original user account.
  • Run Disk Utility: Select your startup disk, click "First Aid" to repair disk permissions and file system errors.

5. Crash Log Clues #

From the crash log you provided, specific error codes can pinpoint the issue:

If you see EXC_BAD_ACCESS in the log, this usually points to a memory access error—likely tied to architecture incompatibility or a damaged plugin.
If NSInvalidArgumentException shows up, it's probably an invalid setting in your preference file causing a load failure.

内容的提问来源于stack exchange，提问作者nicovon