macOS version consumes excessive power and memory, causing high CPU usage and fan noise on launch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Clear and concise description of the problem
On macOS, the Folo desktop application consumes an unusually high amount of memory and CPU immediately after launch.
As soon as the app starts, the system fan spins up aggressively, and overall system performance is noticeably impacted.
This happens even when Folo is idle (no active user interaction or background tasks).
Compared to other Electron-based or native macOS applications, the resource usage is significantly higher.
Suggested solution
- Investigate potential performance issues such as:
-- Unoptimized background processes or polling
-- Excessive rendering or re-render loops
-- Memory leaks or unmanaged resources - Provide performance optimizations for macOS, especially for idle state behavior
- Add basic performance profiling or logging options to help identify resource hotspots
Alternative
No response
Additional context
Platform: Macbook pro M3 16GB macOS
Issue occurs immediately after launch
Fan noise and high power usage persist until the app is closed
No other heavy applications running at the same time
Validations
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
- This issue is valid
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by profiling Folo immediately after launch on macOS while idle, then identify whether background work, rendering, or resource management accounts for the CPU and memory use; done means idle usage is reduced and the hotspot is covered by performance logging or profiling evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, typescript
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100