You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: Profanity ate 1 GB swap in less than 15 days
I have profanity running on a RPi4 (aarch64 architecture) that is running ArchLinuxARM. Profanity receives notifications from e.g. cron jobs and casual interpersonal chat, altogether less than a couple of hundred messages daily — some days substantially less.
The RPi4 has 4 GB RAM + 1 GB swap. Usually no swap is used at all, so at first I didn't notice when free -tk reported that used and free swap had swapped places, so to speak: 100% used swap and 0% free. This was when the RPi4 and profanity had been up for slightly less than 15 days.
A ps ux revealed that the profanity process had gobbled up 2.5+ GB RAM, including all of the available 1 GB swap. Taking profanity down released all of the used swap, except ~40 MB.
Expected Behavior
Ideally, profanity should not keep gobbling up RAM.
Current Behavior
Launching profanity again, this is what I noticed (numbers taken from ps ux):
Regularly run e.g. ps ux | rg pro[f]anity to see its increasing memory consumption
Context
N/A
Environment
Give us the version and build information output generated by profanity -v
$ profanity -v
Profanity, version 0.14.0
Copyright (C) 2012 - 2019 James Booth <[email protected]>.
Copyright (C) 2019 - 2023 Michael Vetter <[email protected]>.
License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Build information:
XMPP library: libstrophe
Desktop notification support: Enabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.23.2)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.11.6)
GTK icons/clipboard: Disabled
GDK Pixbuf: Enabled
If you could not yet build profanity, mention the revision you try to build from
TL;DR: Profanity ate 1 GB swap in less than 15 days
I have profanity running on a RPi4 (aarch64 architecture) that is running ArchLinuxARM. Profanity receives notifications from e.g. cron jobs and casual interpersonal chat, altogether less than a couple of hundred messages daily — some days substantially less.
The RPi4 has 4 GB RAM + 1 GB swap. Usually no swap is used at all, so at first I didn't notice when
free -tk
reported that used and free swap had swapped places, so to speak: 100% used swap and 0% free. This was when the RPi4 andprofanity
had been up for slightly less than 15 days.A
ps ux
revealed that theprofanity
process had gobbled up 2.5+ GB RAM, including all of the available 1 GB swap. Takingprofanity
down released all of the used swap, except ~40 MB.Expected Behavior
Ideally,
profanity
should not keep gobbling up RAM.Current Behavior
Launching
profanity
again, this is what I noticed (numbers taken fromps ux
):HH:MM
is wallclock hours and minutes.I tried the same thing on a x86_64 desktop pc, running ArchLinux:
Possible Solution
I haven't got a clue.
Steps to Reproduce (for bugs)
profanity
in a terminal emulatorps ux | rg pro[f]anity
to see its increasing memory consumptionContext
N/A
Environment
profanity -v
Options used when building the package can be seen here:
Cheers.
The text was updated successfully, but these errors were encountered: