# \[RLlib\] GPU Memory Leak? Tune + PPO, Policy Server + Client

**URL:** <https://discuss.ray.io/t/rllib-gpu-memory-leak-tune-ppo-policy-server-client/10763>\
**Category:** RLlib\
**Created:** [May 23, 2023, 8:53pm UTC](https://discuss.ray.io/t/rllib-gpu-memory-leak-tune-ppo-policy-server-client/10763 "2023-05-23T20:53:42Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![kourosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/kourosh/32/2130_2.png) [@kourosh](https://discuss.ray.io/u/kourosh)\
**Post date:** [May 26, 2023, 7:52pm UTC](https://discuss.ray.io/t/rllib-gpu-memory-leak-tune-ppo-policy-server-client/10763/15 "2023-05-26T19:52:14Z")

</div>

ok so, I would recommend trimming down the configs even further to understand the cause of the leak. There could be two possibilities here:

1. There is a fundamental bug within rllib that was not discovered so far
2. It could be observation space related which either could be wrong usage of something or again a bug for certain class of spaces.

If it’s a bug. you can share the trimmed down version of repro code on a github issue and we will triage it and respond as soon as possible. There is a chance that in the process you may find the solution and in that case your contribution is ofc. welcomed.

We recently also shared a high level debugging [guide](https://discuss.ray.io/t/mini-forum-guide-self-help-guide/10793). I hope that helps in narrowing down the issue.

---

_[View the full topic](https://discuss.ray.io/t/rllib-gpu-memory-leak-tune-ppo-policy-server-client/10763)._