Feedback/Possible Memory leak on 2026.4.0

Possible Memory leak on 2026.4.0

G G·13 days ago

Needs ReproductionBug

Consumed 42GB memory while idling, over the course of 3 hours being open.

After rebooting and running ramwise against it for about 5 minutes:

After about 30 min:

This is all while just idle. I am not using yaak, though it is in the foreground on a workspace.

Happy to provide any logs you are interested in, just let me know how to grab em.

I’m on Pop!_OS 24.04 LTS, using the AppImage

Linux2026.4.0

Comments (4)

Gregory Schier

changed status toNeeds Reproduction·9 days ago

Hmm, I’m not able to reproduce this with the AppImage installer.

Can you try running this to narrow down further where the leak is coming from?

# Replace <pid> with process ID
tr '\0' ' ' < /proc/<pid>/cmdline
ps -o pid,ppid,stat,etime,rss,cmd -p <pid>
sed -n '1,30p' /proc/<pid>/smaps_rollup

Gregory Schier

changed status toIn Progress·9 days ago

Will take a look at this

Hooman Yarahmadi·10 days ago

i am also facing with same issue it stop me from login

nervocalm ·9 days ago

Hi bud! I am on Arch/Plasma/X11, and today I had it open all day and did not have any memory issues.

As I am using yaak-bin 2026.4.0-1 from AUR, it does not seem to be a yaak issue but something more inherent to the distribution format. As you described it, it could be an AppImage “virtualization” issue. Try switching to another binary build or build it from source.