ForgejoGoroutineLeak #

Meaning #

Based on the 6-hour trend, the Forgejo goroutine count is predicted to exceed 10,000 within 1 hour. This indicates a potential goroutine leak in the Forgejo process.

Impact #

A goroutine leak will eventually exhaust memory and CPU, causing Forgejo to become unresponsive or crash.

Diagnosis #

Check the current goroutine count in Prometheus:

go_goroutines{job="forgejo"}

Check Forgejo logs via the PikaPods dashboard for errors or repeated operations.

Mitigation #

Restart the Forgejo instance via the PikaPods dashboard to reset the goroutine count. If the leak recurs, check the Forgejo version for known issues and consider upgrading. Contact PikaPods support if the issue persists.