// troubleshooting guide · docfetcher

DocFetcher Out of Memory: How to Increase the Memory Limit

Status
Workaround available
platforms:
Windows, macOS, Linux
updated:
November 19, 2026
reports:
3
Method
how we research
Share

RUNBOOK · docfetcher/out-of-memory5 FIXES

// quick answer

DocFetcher runs on Java with a fixed heap limit set by -Xmx in its launcher. Raise it (for example to -Xmx4g on an 8 GB PC) and big indexes stop hanging and crashing.

Most likely fix: Windows installed version

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Windows installed version

    1. 01Move misc\DocFetcher.bat up one level into the DocFetcher program folder
    2. 02Open it in a text editor and change -Xmx on the last line, e.g. -Xmx4g
    3. 03Always launch DocFetcher by double-clicking DocFetcher.bat
    Did this fix it?
  2. FIX 2Linux and macOS

    1. 01Open DocFetcher.sh (on macOS inside the .app bundle under Contents/MacOS) in a text editor
    2. 02Change the -Xmx value, e.g. -Xmx4g
    3. 03Start DocFetcher from that script
    Did this fix it?
  3. FIX 3PortableApps version

    1. 01Open App\AppInfo\Launcher\DocFetcherPortable.ini
    2. 02In the CommandLineArguments= line change -Xmx, e.g. -Xmx4g
    Did this fix it?
  4. FIX 4Linux snap

    1. 01Run docfetcher from a terminal
    2. 02The startup message names the config file where the memory setting lives; edit it and restart
    Did this fix it?
  5. FIX 5Reduce memory pressure

    1. 01Index subfolders separately with the + button in the indexing dialog
    2. 02Keep at least 1 GB of free disk space for index files
    3. 03Rebuild any index that crashed while memory was too low
    Did this fix it?

SANDBOX · docfetcher RUNS IN YOUR BROWSER

Try it: a launcher with snippets and clipboard history

A hands-on DocFetcher-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

Indexing slows to a crawl, hangs or crashes with OutOfMemoryError on large folders; the app becomes unresponsive with big indexes loaded.

Why it happens

  • C-01Default Java heap too small for large document sets
  • C-02Very large single files (huge PDFs, archives)
  • C-0332-bit Java capping memory at about 1 GB on old setups

// this guide also covers

  • docfetcher out of memory
  • docfetcher memory limit
  • docfetcher increase memory
  • docfetcher java heap space
  • docfetcher xmx

Still not working?

If DocFetcher keeps failing, you're not alone. See every DocFetcher problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch DocFetcher Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other DocFetcher errors

All 10 DocFetcher errors and fixes →