kambei opened a new issue, #3159: URL: https://github.com/apache/apisix-dashboard/issues/3159
### Issue description ## Summary The APISIX Dashboard pod (`apisix-dash-ins`) has a severe resource leak, affecting both **CPU and Memory**. Our monitoring graphs show a simultaneous and continuous increase in both metrics over time. This makes the dashboard highly unstable for production use, as it inevitably leads to the pod being terminated by Kubernetes (**OOMKilled**) and can contribute to CPU pressure on the node. --- ## Observed Behavior We've been monitoring the APISIX Dashboard pod and have identified two parallel issues: 1. **CPU Leak**: The pod's CPU consumption grows in a steady, linear fashion. It starts near zero and climbs continuously without flattening. This suggests an accumulation of unterminated background processes or a persistent busy-wait loop. 2. **Memory Leak**: Concurrently, the memory usage shows a steady, step-wise increase. Following a pod restart, the memory footprint consistently grows and never returns to a stable baseline. The combination of both resources growing uncontrollably points to a fundamental bug in the application's resource management. ### Expected behavior The CPU and Memory usage of the `apisix-dashboard` pod should remain relatively stable and not grow indefinitely. Resources should be released after tasks are completed. ### How to Reproduce 1. Deploy the specified version of the APISIX Dashboard on a Kubernetes cluster. 2. Set up monitoring for the pod's CPU and Memory usage (e.g., with Prometheus/Grafana). 3. Let the dashboard run for 12-24 hours. 4. Observe the graphs for both CPU and Memory, which will show a continuous upward trend. 5. Check the pod's restart count using `kubectl get pods`, which will likely increase over time. ### Screenshots <img width="1604" height="682" alt="Image" src="https://github.com/user-attachments/assets/cd09029b-28f6-4dcd-b715-c3eb7c4735ea"; /> <img width="1618" height="826" alt="Image" src="https://github.com/user-attachments/assets/621f2963-c805-4a88-9259-84728d00c1fc"; /> ### Environment * **APISIX Dashboard Version**: `3.0.1-alpine` * **Installation Method**: `Dockerfile with Deployment and custom conf.yaml` ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
