If Parsec closes unexpectedly or becomes unresponsive, here’s how to grab the information necessary to report it to someone.

Parsec crashed (closed unexpectedly)

If Parsec closes unexpectedly and then re-opens, do this.

Windows

• Enable Parsec’s ability to generate minidumps
  • Press Windows key + R
  • Type the path for the config file
    • Per user installation: Type %appdata%\\Parsec\\config.txt
    • Shared installation: Type %programdata%\\Parsec\\config.txt
  • Press Enter. A text file will open
  • Add a line to the bottom of the file: app_write_minidump=true
  • Save the text file
  • Right-click the Parsec icon in your taskbar on the bottom-right
  • Select Restart
• Reproduce the issue that causes the crash
• Find the dump file generated by the app
  • Press Windows key + R
  • Type the folder path: %programdata%\\ParsecPersistent
  • Locate the parsec.dmp file
    • It might instead be on %temp% or %systemroot%\\Temp on old versions of the app

You can drag and drop the file onto Discord in private messages to a Parsec Team member. Please ensure to also describe the steps you take to trigger a crash, along with the file.

macOS

• Open the Console (not Terminal) app built into macOS
• Click the Crash Reports section to the side
• There will be a list of recent crashes. Find Parsec crashes with the name parsecd
• Right-click and select ‘Reveal in Finder’

You can drag and drop the file onto Discord in private messages to a Parsec Team member. Please ensure to also describe the steps you take to trigger a crash, along with the file.

Linux

Files may be located in /var/crash. You can use cd /var/crash to move into this directory, and xdg-open . to open in a file explorer.

You can drag and drop the file onto Discord in private messages to a Parsec Team member. Please ensure to also describe the steps you take to trigger a crash, along with the file.

Parsec froze (is open but unresponsive)

If Parsec is not responding and never goes back to working, rather than completely closing, do this.

Windows