// troubleshooting guide · gitea
Why Is Gitea Using So Much Memory or CPU?
- Status
- Ongoing
- platforms:
- Self-hosted
- updated:
- November 16, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · gitea/high-memory-cpu4 FIXES
// quick answer
The code indexer and repository mirroring are the usual culprits. Disable or move the indexer and check for version-specific regressions.
Most likely fix: Disable the repo indexer to test
How to fix it
// try these in order, the most common fix is first
FIX 1Disable the repo indexer to test
- 01Set REPO_INDEXER_ENABLED = false in [indexer]
- 02Restart and watch memory
Did this fix it?FIX 2Use Elasticsearch
- 01Switch the indexer to Elasticsearch, which one user found lighter than bleve on disk
Did this fix it?FIX 3Check version and upgrade
- 01Compare against Gitea issues 31565 and 33809
- 02Upgrade to the latest patch release
Did this fix it?FIX 4Inspect processes
- 01Look for git subprocesses in htop
- 02Review Site Administration > Monitoring
Did this fix it?
SANDBOX · gitea RUNS IN YOUR BROWSER
Try it: push, review, run CI and merge in a code host and cloud workspace
A hands-on Gitea-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Memory climbs until out-of-memory, CPU stays high after an upgrade, or memory does not drop after mirrors sync.
Why it happens
- C-01Repo indexer (bleve) on large instances
- C-02Regression after upgrade such as 1.22 to 1.23 reports
- C-03Mirror sync memory not released
- C-04Git child processes on large repositories
// this guide also covers
- gitea high memory usage
- gitea high cpu
- gitea out of memory
Still not working?
If Gitea keeps failing, you're not alone. See every Gitea 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 slow, laggy or resource-hungry guides →
Why Is GitLab So Slow? (GitLab)
Why Is Azure DevOps Boards So Slow? (Azure DevOps)
Other Gitea errors
- Gitea Actions Jobs Stuck in Waiting (No Matching Runner)
- Gitea SSH Permission Denied (publickey) or Connection Refused
- Gitea 500 Internal Server Error
- Gitea Reverse Proxy Wrong URLs or Redirect Loop (ROOT_URL)
- Gitea Push 413 Request Entity Too Large (LFS Upload Fails)
- Gitea Webhook Not Working (ALLOWED_HOST_LIST Error)
- Gitea Email Notifications Not Sending (SMTP Error)
- Gitea Upgrade Failed or Database Is Locked