Skip to content

ArchiveMind is running but using 0% CPU

Symptoms

Activity Monitor or Task Manager shows the ArchiveMind process alive but using little or no CPU, and you expected it to be doing something.

What this usually means

Idle is the normal state. ArchiveMind keeps its local server running so the interface stays available after a scan finishes — an open, idle ArchiveMind at 0% CPU means "ready", not "stuck". Other common cases:

  • Waiting on a slow drive. During a scan of a slow USB drive or network share, the bottleneck is the drive: the process can sit near 0% CPU while it waits for data. Look at disk activity, not CPU.
  • The scan simply finished. Check the interface — if it reports the scan complete, the process staying alive is by design. See Reopening ArchiveMind.

Safe steps to try

  1. Open the interface (http://127.0.0.1:8765/) and look at what it says: scan complete, scan in progress, or an error.
  2. If a scan should be running, check disk activity (Activity Monitor's Disk tab / Task Manager's Performance tab) — reads mean work.
  3. If you are done using ArchiveMind and just want it to stop running, quit it properly: Quit ArchiveMind in the top-right corner.

What not to delete or change

  • Do not force-kill the process just because it is idle — quitting via the button is the clean path.
  • Do not delete the catalogue database.

Information to collect for support

Only needed if the interface claims work is in progress while nothing — CPU or disk — happens for a long time:

  • A screenshot of the progress panel.
  • The newest archivemind.log — see Finding logs.