Yaak Logo
Yaak
Feedback/Yaak uses excessive memory and CPU while idle (Possible Memory leak)

Yaak uses excessive memory and CPU while idle (Possible Memory leak)

Jakariya Abbas·a month ago·#YF1029
ReleasedBug

When Yaak is left idle in the background without any user interaction, it consumes approximately 9 GB of RAM and 30% CPU. This happens even when no requests are running and the application is not being actively used.

Actual behavior: RAM usage: ~9 GB. CPU usage: ~30%. No user interaction or active requests.

Expected behavior: Resource usage should remain low while the application is idle in the background.

System:

CPU: Intel Core i5-8365U

Kernel: Linux 7.1.3-2-cachyos x86_64

Memory: 15.24 GiB

Linux2026.4.0

Comments (10)

Sign in to leave a comment.

Gregory SchierNeeds Reproduction

Have you added a Git repo to any Yaak workspaces? I have some improvements for this in the latest Beta 7

https://github.com/mountain-loop/yaak/releases/tag/v2026.5.0-beta.7

Jakariya AbbasOP

Yes. The workspace in question falls under GitHub repo. (Not independent but nested under the project repository)

Gregory Schier

Can you try the new beta to see if it helps?

Jakariya AbbasOP

Sure. I’ll let you know

Jakariya AbbasOP

The bug did not appear in the beta version as of using for few weeks.

Arturs Jurgevics

I have the same behavior on Linux Fedora with i5-11500, latest 2026.4.0. Was very surprised when found it

Jakariya AbbasOP

And that issue is annoying me. do you know of any better API testing client? with the similar or more features as yaak?

Sanjai Kumar

@Jakariya Abbas

There are n API clients in the market, and each has its own things that can “annoy” a user. Only with the user’s help can one make an app less annoying. That said, did you try the beta version Greg mentioned?

https://github.com/mountain-loop/yaak/releases/tag/v2026.5.0-beta.7

Jakariya AbbasOP

Yeah I have. And the bug didn’t appear in the beta version.

Yaak Bot

This is fixed in 2026.5.0. The cause was the Git status watcher scanning the entire containing repository instead of just the sync directory, which is why it only appeared for workspaces nested inside a larger repo. Thanks for running the beta for a few weeks to confirm.

Type to search feedback...