// troubleshooting guide · docfetcher
DocFetcher Crashes With 'Program Died' Error
- Status
- Workaround available
- platforms:
- Windows, macOS, Linux
- updated:
- November 19, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · docfetcher/program-died-crash5 FIXES
// quick answer
DocFetcher crashes during indexing are usually a parser choking on one bad file or the Java memory limit being hit. Update to 1.1.27, raise the memory limit, index subfolders separately and rebuild the broken index.
Most likely fix: Update to the latest version
How to fix it
// try these in order, the most common fix is first
FIX 1Update to the latest version
- 01Download DocFetcher 1.1.27 from docfetcher.sourceforge.io/download
- 02For portable installs, copy your old conf and indexes folders into the new DocFetcher folder
Did this fix it?FIX 2Raise the memory limit
- 01Close DocFetcher
- 02Edit the -Xmx value in the launcher (see the memory guide), for example -Xmx4g
- 03Do not set it above your physical RAM
Did this fix it?FIX 3Rebuild the crashed index
- 01Right-click the index in the Search Scope pane
- 02Choose Rebuild Index; a partial index from a crash may be broken even after you fix the cause
Did this fix it?FIX 4Index subfolders one at a time
- 01In the indexing dialog, use the + button at the top right to queue subfolders
- 02One failing folder then no longer kills the whole run
Did this fix it?FIX 5Re-save or exclude problem files
- 01Note the file named in the error or last processed
- 02Re-save old Office files in a newer format, for example with LibreOffice
- 03Or exclude it with a regex rule in the indexing dialog's pattern table
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
A dialog says the program just died, often with a Java stack trace (SWTException, AssertionError, OutOfMemoryError), usually partway through building an index.
Why it happens
- C-01A malformed or unusual Office, PDF or image file crashing a third-party parser (Apache POI, PDFBox, metadata readers)
- C-02Java memory limit too low for the folder size
- C-03Outdated DocFetcher version with since-fixed parser bugs
- C-04Index left half-built by an earlier crash
// this guide also covers
- docfetcher program died
- docfetcher crash
- docfetcher crashes while indexing
- docfetcher error
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 usThe same problem in other apps
All crashes, freezes & blank screens guides →
AnyTXT Crashes on Startup or When Searching (AnyTXT Searcher)
Other DocFetcher errors
- DocFetcher Out of Memory: How to Increase the Memory Limit
- DocFetcher Won't Start or Open
- DocFetcher Not Finding Text in Files
- DocFetcher Not Searching Scanned PDFs
- DocFetcher 'Folder Hierarchy Is Too Deep' Error
- DocFetcher High CPU Usage
- DocFetcher Index Not Updating
- Outlook Won't Start After DocFetcher Indexing