Possible memory leak

[aionkonata]

EasyEffects Version

8.1.8

What package are you using?

Arch (easyeffects)

Distribution

CachyOS 6.19.10

Describe the bug

Works as normal for a while, don't have an exact timeframe (seems to be 1-2 hours) but eventually EasyEffects will be killed citing low kernel memory available.

Expected Behavior

EasyEffects runs in the background and processes audio, is not killed due to OOM

Debug Log

Debug Log

Output from journalctl -xe

Apr 04 19:18:11 skaia kernel: easyeffects invoked oom-killer: gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|__GFP_COMP), order=0, oom_score_adj=200
Apr 04 19:18:11 skaia kernel: CPU: 10 UID: 1000 PID: 1487517 Comm: easyeffects Tainted: G           O        6.19.10-1-cachyos #1 PREEMPT(full)  8fe356e4fe4ee3008a8a5c70007cff4a4699e1ce
Apr 04 19:18:11 skaia systemd[1702]: app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service: The kernel OOM killer killed some processes in this unit.
Apr 04 19:18:11 skaia kernel: [1487517]  1000 1487517 17478687  7479520  7439176    39931       413 116183040  6908064           200 easyeffects
Apr 04 19:18:11 skaia kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service,task=easyeffects,pid=1487517,uid=1000
Apr 04 19:18:11 skaia kernel: Out of memory: Killed process 1487517 (easyeffects) total-vm:69914748kB, anon-rss:29756704kB, file-rss:159724kB, shmem-rss:1652kB, UID:1000 pgtables:113460kB oom_score_adj:200
Apr 04 19:18:13 skaia kernel: oom_reaper: reaped process 1487517 (easyeffects), now anon-rss:56kB, file-rss:15368kB, shmem-rss:1652kB
Apr 04 19:18:13 skaia systemd[1702]: app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service: Main process exited, code=killed, status=9/KILL
Apr 04 19:18:13 skaia systemd[1702]: app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service: Failed with result 'oom-kill'.
Apr 04 19:18:13 skaia systemd[1702]: app-com.github.wwmm.easyeffects@311a2894deef4bfcb64618d9c41b446f.service: Consumed 44min 16.493s CPU time over 2h 35min 29.240s wall clock time, 29.8G memory peak, 26.3G memory swap peak.

29.8G memory peak

Additional Information

I have a feeling this might be related to the spectrum being enabled. I will turn the spectrum off and see if the problem is resolved.

[aionkonata]

I unfortunately didn't have easyeffects running with G_MESSAGES_DEBUG=easyeffects before the OOM happened. I hope the journalctl snippet is acceptable. I'm currently running easyeffects with the debug messages turned on while testing to see if it happens again with the Spectrum disabled.

[wwmm]

Hum... Which plugins were you using? Your oom reports that EasyEffects was using almost 30 GB. But when I do tests with the compilter sanitizer, what considerably increases the app memory usage, it barely gets close to 1GB. And I would expect such a massive leak to be affecting more people.

[aionkonata]

I am using a Gate, Compressor, Multiband Compressor, Limiter, and Loudness contour. All from lsp-plugins.

[wwmm]

If possible share your preset file.

[aionkonata]

Here's my preset.

[wwmm]

I did some tests but so far I did not see anything that could explain a 30 GB memory leak. It seems normal. I think that the only thing we can do right now is observe the situation and trying to find out what it is that triggered this.

[aionkonata]

It's been about an hour since testing with the spectrum disabled. RAM usage looks normal (around 300mb). Will continue to monitor and update if anything changes

(for reference, the spectrum was set to the Area shape with everything else default)

[wwmm]

The code path used for the area graph is almost the same as the one used for the others. The only way I can see it causing a leak is if QtGraphs has a leak in its area graph code. But in the limited tests I did it seemed fine.

[aionkonata]

~13 hours later, easyeffects has been open the entire time and has not suffered another memory leak. ~200mb memory usage and nothing concerning in the debug output.

[wwmm]

~13 hours later, easyeffects has been open the entire time and has not suffered another memory leak. ~200mb memory usage and nothing concerning in the debug output.

I wonder if maybe a different process was using 30 GB and it just happened that easyeffects asked for more ram when there wasn't and the oom mentioned easyeffects just because it did the most recent memory allocation attempt. Usually it isn't so hard to reproduce a massive memory leak.

[aionkonata]

I wonder if maybe a different process was using 30 GB and it just happened that easyeffects asked for more ram when there wasn't and the oom mentioned easyeffects just because it did the most recent memory allocation attempt. Usually it isn't so hard to reproduce a massive memory leak.

that may have been what happened. i'll keep tabs on my ram usage and see if anything happens over the next few days.