# \[solved\] Zammad memory leak?

**URL:** https://community.zammad.org/t/solved-zammad-memory-leak/1806
**Category:** Technical assistance
**Created:** [December 17, 2018, 9:30am UTC](https://community.zammad.org/t/solved-zammad-memory-leak/1806 "2018-12-17T09:30:11Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![SEGGER-NV](https://community.zammad.org/letter_avatar_proxy/v4/letter/s/ee59a6/32.png) [@SEGGER-NV](https://community.zammad.org/u/SEGGER-NV)
#### Post date: [December 19, 2018, 10:14am UTC](https://community.zammad.org/t/solved-zammad-memory-leak/1806/12 "2018-12-19T10:14:52Z")

</div>

Hi,

Agreed that it is not a solution but a mere workaround.  
Our PGSQL config has only changed in default in max\_connections from default 100 to 200 as we got internal 500 errors when increasing web\_concurrecny.  
See here for more info: [[SOLVED] Internal server error 500 when WEB\_CONCURRENCY is set \>1 - #5 by SEGGER-NV](https://community.zammad.org/t/solved-internal-server-error-500-when-web-concurrency-is-set-1/1657/5)

However these two changes started the slow but constant increase of memory usage.

> [@MrGeneration](#):
>
> Problem is, dozens of people use Zammad in productive with even more concurrent active agents.

Do they have regular maintenance periods where servers or services might be restarted?  
Or do they have 0 maintenance 100% uptime setups?

> [@MrGeneration](#):
>
> Small hint regarding killing of processes: This is a linux behavior you can configure.  
> And another thing: You should always try to avoid to use swap, as your systems performance will decrease significantly.

Fair enough, but it should have never gotten to that point. The swappiness of the system is currently set to start using swap if less than 10% memory are available.

Br,  
Nino

---

_[View the full topic](https://community.zammad.org/t/solved-zammad-memory-leak/1806)._