CPU 异常占用 #14266

Closed
opened 2025-11-02 11:08:01 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @zhk0603 on GitHub (Mar 18, 2025).

Description

第一次创建的时候,是正常的,我重启服务器(ESIX,控制面板直接重启)之后CPU异常占用

Image

Gitea Version

1.24.0+dev-449-g1ea5216f4a

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

networks:
gitea:
external: false

services:
server:
image: docker.io/gitea/gitea:nightly
container_name: gitea
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /mnt/data/gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "13000:3000"
- "12222:22"

Database

None

Originally created by @zhk0603 on GitHub (Mar 18, 2025). ### Description 第一次创建的时候,是正常的,我重启服务器(ESIX,控制面板直接重启)之后CPU异常占用 ![Image](https://github.com/user-attachments/assets/ee8fd43e-e868-44a1-861f-6a6f1809d2fa) ### Gitea Version 1.24.0+dev-449-g1ea5216f4a ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? networks: gitea: external: false services: server: image: docker.io/gitea/gitea:nightly container_name: gitea environment: - USER_UID=1000 - USER_GID=1000 restart: always networks: - gitea volumes: - /mnt/data/gitea:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro ports: - "13000:3000" - "12222:22" ### Database None
GiteaMirror added the issue/needs-feedbacktype/bug labels 2025-11-02 11:08:01 -06:00
Author
Owner

@zhk0603 commented on GitHub (Mar 18, 2025):

Image
疯狂

@zhk0603 commented on GitHub (Mar 18, 2025): ![Image](https://github.com/user-attachments/assets/a2749501-d7fc-4729-ba5f-4acf5a7afa0a) 疯狂
Author
Owner

@wxiaoguang commented on GitHub (Mar 18, 2025):

This issue report doesn't contain informative content.

At least, you need to clarify which process consumes that CPU, and provide evidence.

Only providing a CPU usage screenshot means nothing, what if it is a ESXi bug (some users ever reported similar problems and they said that doing a whole host reboot fixed the problem) or your server was hacked and somebody is mining on it?

@wxiaoguang commented on GitHub (Mar 18, 2025): This issue report doesn't contain informative content. At least, you need to clarify which process consumes that CPU, and provide evidence. Only providing a CPU usage screenshot means nothing, what if it is a ESXi bug (some users ever reported similar problems and they said that doing a whole host reboot fixed the problem) or your server was hacked and somebody is mining on it?
Author
Owner

@zhk0603 commented on GitHub (Mar 20, 2025):

This issue report doesn't contain informative content.

At least, you need to clarify which process consumes that CPU, and provide evidence.

Only providing a CPU usage screenshot means nothing, what if it is a ESXi bug (some users ever reported similar problems and they said that doing a whole host reboot fixed the problem) or your server was hacked and somebody is mining on it?

@wxiaoguang This is my internal network server, so it shouldn't be vulnerable to hacker attacks. In the Gitea admin panel, I noticed that garbage collection (GC) was happening very frequently, every few seconds. However, after I restarted the container, it returned to normal.

@zhk0603 commented on GitHub (Mar 20, 2025): > This issue report doesn't contain informative content. > > At least, you need to clarify which process consumes that CPU, and provide evidence. > > Only providing a CPU usage screenshot means nothing, what if it is a ESXi bug (some users ever reported similar problems and they said that doing a whole host reboot fixed the problem) or your server was hacked and somebody is mining on it? @wxiaoguang This is my internal network server, so it shouldn't be vulnerable to hacker attacks. In the Gitea admin panel, I noticed that garbage collection (GC) was happening very frequently, every few seconds. However, after I restarted the container, it returned to normal.
Author
Owner

@wxiaoguang commented on GitHub (Mar 20, 2025):

Please refer to this one:

If there are new clues, feel free to reopen.

@wxiaoguang commented on GitHub (Mar 20, 2025): Please refer to this one: * https://github.com/go-gitea/gitea/issues/31956#issuecomment-2626696262 If there are new clues, feel free to reopen.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14266