uwsgi memory usage
Hi Folks, I think there's a memory leak somewhere in the system. Over time, on a relatively small set of lists, I see the uwsgi process grow and grow until the system OOMs.
I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem?
Peter C
On 6/28/22 18:13, peter@chubb.wattle.id.au wrote:
Hi Folks, I think there's a memory leak somewhere in the system. Over time, on a relatively small set of lists, I see the uwsgi process grow and grow until the system OOMs.
I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem?
We are not seeing this on any of the sites I manage including mail.python.org and lists.mailman3.org, but we install the latest source from GitLab and we use gunicorn, not uWSGI.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
peter@chubb.wattle.id.au writes:
Over time, on a relatively small set of lists, I see the uwsgi process grow and grow until the system OOMs.
As Mark points out, those of us who use gunicorn (an alternative WSGI provider to interface Mailman to the web server) don't see this. Since you see it specifically in the uswgi process and we don't see it at all, this pretty well localizes it to uwsgi. This is a 3rd party application not maintained by Mailman or Debian, and the uswgi project (not Debian) is likely the best place to get help.
Is it a Debian issue, a local config issue, or a general problem?
Based on the relatively small amount of information, I think it's most likely to be a defect in upstream uwsgi. But the uswgi developers are the best people to answer that, and you almost certainly need them to develop a fix.
Steve
Hello,
On Wed, Jun 29, 2022 at 11:13:17AM +1000, peter@chubb.wattle.id.au wrote:
I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem?
Just to say, I think I'm seeing this too. Using the packaged uwsgi on Debian stable. After a week or so, uwsgi is using 7% RAM. Restarted it via restarting mailman3-web and the uwsgi process is back to 1% RAM.
I'll follow along your Debian bug report.
Cheers, Andy
"Andy" == Andy Smith <andy@strugglers.net> writes:
On Wed, Jun 29, 2022 at 11:13:17AM +1000, peter@chubb.wattle.id.au wrote:
I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem?
Andy> Just to say, I think I'm seeing this too. Using the packaged Andy> uwsgi on Debian stable. After a week or so, uwsgi is using 7% Andy> RAM. Restarted it via restarting mailman3-web and the uwsgi Andy> process is back to 1% RAM.
Bug report is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014037
Peter C
participants (4)
-
Andy Smith -
Mark Sapiro -
peter＠chubb.wattle.id.au -
Stephen J. Turnbull