SaaS Metrics
Gemini Executive Synthesis
Memory leak, PDF processing, indexing stability.
Technical Positioning
Resource-efficient, stable background operation, robust file handling.
SaaS Insight & Market Implications
This issue details a severe memory leak within DigUp's indexing service, specifically triggered by macOS's PDF text reader getting stuck on certain PDF files. The reported memory consumption reaching 55GB is a critical stability and performance defect. Such resource inefficiency will lead to system instability and user frustration, directly undermining DigUp's value proposition as an on-device search tool. While a temporary workaround exists, a robust fix for problematic file handling is essential. This impacts the product's reliability and its ability to operate seamlessly in the background, a core expectation for such utilities.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
GitHub Issue
Oct 11, 2026
Repo: ARahim3/DigUp
Excessive memory use whenever leaving app open for a decent amount of time
Memory usage consistently increase by ~0.15 GB per second around 5 minutes after opening the app (I assume when indexing).
It goes up to 55GB and then drops down to around 35, and rises again. repeat.
Developer Debate & Comments
It doesn't seem to know its limits.
Hi @jiaxu0715, thanks for reporting. I am looking into it.
Hi @jiaxu0715. I haven't been able to reproduce this on my Mac yet, so could you help me with two things? 1. Your Mac model, RAM and macOS version. 2. While the memory is climbing, paste this into Terminal, then share the output and the two files it saves to your Desktop: ``` pid=$(pgrep -f "digup index-service") lsof -p $pid | grep -v -e /System/ -e /usr/ -e /dev/ -e /private/ -e /Library/ sample $pid 5 -file ~/Desktop/digup-sample.txt footprint $pid > ~/Desktop/digup-footprint.txt ``` Feel free to blank out file names.
[digup-footprint.txt](https://github.com/user-attachments/files/33304163/digup-footprint.txt) [digup-sample.txt](https://github.com/user-attachments/files/33304166/digup-sample.txt)
Thanks @jiaxu0715, the sample showed the problem. macOS's own PDF text reader gets stuck on a page in one of your PDFs and keeps using more memory. Until I fix it: 1. Open DigUp's Settings → Folders and add `pdf` under "Skip these file types". 2. Force quit `digup` in Activity Monitor. DigUp starts it again, without PDFs. I'm working on a fix so DigUp skips a file like this by itself. If you can, this shows which PDF it is while the memory is climbing: ``` lsof -p $(pgrep -f "digup index-service") | grep -i '\.pdf'
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from ARahim3/DigUp.
Extracted Positioning
Local index encryption, data security at rest.
Enhanced privacy and security for sensitive local data, enterprise-grade data protection.
Extracted Positioning
Homebrew Cask installation, package manager support.
Developer-friendly installation, integration with macOS ecosystem tools.
Windows
1
Extracted Positioning
Windows platform support.
Cross-platform availability, expanded market reach.
Extracted Positioning
Linux CLI port, cross-platform engine, binary distribution.
Expanded platform reach for core search capabilities, developer-focused tooling, robust cross-platform indexing.
Extracted Positioning
Model download mechanism, firewall compatibility, manual model specification.
Robust deployment in restricted network environments, flexible configuration.
Frequently Asked Questions
Market intelligence mapped to Memory leak, PDF processing, indexing stability..
What problem does Memory leak, PDF processing, indexing stability. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Resource-efficient, stable background operation, robust file handling.
What is the general sentiment around Memory leak, PDF processing, indexing stability.?
Yes, we have tracked 8 direct responses and active debates regarding this specific topic originating from GitHub Issue.
What are the foundational technologies related to Memory leak, PDF processing, indexing stability.?
Our proprietary extraction maps Memory leak, PDF processing, indexing stability. to adjacent architectural concepts including Excessive memory use, memory usage consistently increase, indexing, Mac model.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like RAM and indexing by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.