# Pod memory overflow

**URL:** <https://discuss.kubernetes.io/t/pod-memory-overflow/29123>\
**Category:** General Discussions\
**Created:** [July 24, 2024, 10:52am UTC](https://discuss.kubernetes.io/t/pod-memory-overflow/29123 "2024-07-24T10:52:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rlws1600510083](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rlws1600510083/32/15430_2.png) [@rlws1600510083](https://discuss.kubernetes.io/u/rlws1600510083)\
**Post date:** [July 24, 2024, 10:52am UTC](https://discuss.kubernetes.io/t/pod-memory-overflow/29123/1 "2024-07-24T10:52:49Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version: v1.26.5  
Host OS: centos8  
CNI and version: cni-plugins-linux-arm64-v1.3.0  
containerd version: containerd [GitHub - containerd/containerd: An open and reliable container runtime](http://github.com/containerd/containerd) v1.7.1 1677a17964311325ed1c31e2c0a3589ce6d5c30d

Question：

I allocated 64Gi of memory to a Deployment and started an algorithm process in it. After a period of time (about an hour), it was found that the process occupied a large amount of memory 400Gi, causing the host to crash OOM.

When the Pod is running, you cannot use the ps -aux command or the top command to check that the memory usage of the process has become high. However, you can use free -h to find that the memory usage increases until it exceeds the Pod memory limit and causes the system to crash due to OOM.

The configuration file is as follows:

```auto
        command: ["sh", "-c"]
        args:
          - cd /home/** && python main.py --mode stream --videostream-path data/test.mp4 --weights data/model/yolov5l_310P3.om
        resources:
          limits:
            cpu: "16"
            memory: 64Gi
          requests:
            cpu: "8"
            memory: 32Gi

```

Since I can only upload one picture, I stitched together several pictures and put them in together.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/a/a73e7aef0011b73a1ca2271bdd19fd9203468c8a.png)

---

<div class="post-metadata">

**Author:** ![Alexandru\_Lazarev](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/alexandru_lazarev/32/15427_2.png) [@Alexandru\_Lazarev](https://discuss.kubernetes.io/u/Alexandru_Lazarev)\
**Post date:** [December 13, 2024, 7:21pm UTC](https://discuss.kubernetes.io/t/pod-memory-overflow/29123/2 "2024-12-13T19:21:29Z")

</div>

Hi @rlws1600510083  
I’m just currious if You found root cause of your issue?

I don’t understand how does process consumes 400GB if You settled limit of 64GB?

Can You see your process MEM (RES) usage with top command on host?  
Is Your app working actively with files inside a container?