-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High used of cpu when i run gitea one or two day. #21816
Comments
#10661 |
Are you able to enable pprof and get a stack trace? You'll need to enable pprof in app.ini and restart Gitea
Then when Gitea gets stuck, use curl or browser to visit: http://127.0.0.1:6060/debug/pprof/goroutine?debug=1 (IP must be 127.0.0.1 and port must be 6060). Report the output back here. |
The most likely cause of this is the cron task: repo_health_check which runs at midnight This runs git fsck on your repositories. I suspect you have a repo that needs to be fsck'd and looked at |
OK. I will try |
Sometime i also get in day time. |
Could you help check this? Thanks. Could not push once more. Need restart. |
when i push new data, gitea create new thread and it take 100 % . i restart the gitea this thread still exist. need kill the pid manually |
Do you build Gitea yourself or where did you download it? |
|
After #24636 (1.20 nightly at the moment) You can download the CPU profile from you admin page. Then we can know what happens. |
Feel free to re-open if there are new clues. |
Description
I need restart to fix it.
Gitea Version
1.17.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Mac mini M1
How are you running Gitea?
gitea &
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: