| Summary: | pavucontrol balloons in memory over several days and becomes sluggish and unwieldy. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Sam Khangyi <khangyi> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | juan.baptiste, mageia, marja11, shlomif |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | pavucontrol | CVE: | |
| Status comment: | |||
|
Description
Sam Khangyi
2016-02-05 07:03:12 CET
elevate should be alleviate ... changing the backend from gstreamer to phonon vlc seems to fix it also noted exiting amarok will stop the leak. will do an experiment with phonon gstreamer as the backend and see what effect that will have. Ok, so phonon gstreamer backend for amarok, will produce the leak again with VLC being the secondary if that is important. You need to logout and login to your X/kde session before changes take effect. 6123 bogi 20 0 699160 46952 33088 S 6.6 0.4 0:05.81 pavucontrol <bogi> 6123 bogi 20 0 699820 47616 33088 S 8.0 0.4 0:08.56 pavucontrol I got my steady leak back again. CC'ing the maintainers of pulseaudio/pavucontrol, phonon-{gstreamer,vlc} and amarok.CC:
(none) =>
juan.baptiste, mageia, shlomif I don't really understand all the details of this bug. How can one reproduce it fully? 6123 bogi 20 0 1053576 401376 33092 S 8.0 3.3 26:36.04 pavucontrol After a good five hours of running. So you need amarok to be running, not necessarily doing anything, just restarting with your system upon reboot or exit/login and pavucontrol will keep leaking.. again. I do run pavucontrol all the time, because of my sound setup, but regardless, it shouldn't leak. (In reply to Sam Khangyi from comment #6) > 6123 bogi 20 0 1053576 401376 33092 S 8.0 3.3 26:36.04 > pavucontrol > > After a good five hours of running. > > So you need amarok to be running, not necessarily doing anything, just > restarting with your system upon reboot or exit/login and pavucontrol will > keep leaking.. again. > > I do run pavucontrol all the time, because of my sound setup, but > regardless, it shouldn't leak. Assigning to Coling, because it is pavucontrol that leaks and I can not imagine the bug then being in e.g. amarok. (Correct me if I'm wrong ;-) ) CC:
(none) =>
marja11 (In reply to Marja van Waes from comment #7) > (In reply to Sam Khangyi from comment #6) > > 6123 bogi 20 0 1053576 401376 33092 S 8.0 3.3 26:36.04 > > pavucontrol > > > > After a good five hours of running. > > > > So you need amarok to be running, not necessarily doing anything, just > > restarting with your system upon reboot or exit/login and pavucontrol will > > keep leaking.. again. > > > > I do run pavucontrol all the time, because of my sound setup, but > > regardless, it shouldn't leak. > > Assigning to Coling, because it is pavucontrol that leaks and I can not > imagine the bug then being in e.g. amarok. (Correct me if I'm wrong ;-) ) Correct, pavucontrol is the leaking application, amarok is merely there to induce the leak, I also found that playing flash games with audio also induces the leak. Even pausing a video on youtube for a long time would induce the leak... Hi Sam, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja (In reply to Marja Van Waes from comment #9) > Hi Sam, > > Thank you for having taken the needed time to report this issue! > > Did this bug get fixed? If so, please change its status to RESOLVED - FIXED > > If it didn't, then we regret that we weren't able to fix it in Mageia 5. > Mageia 5 has officially reached its End of Life on December 31st, 2017 > https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ > It only continued to get important security updates since then, because we > are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the > Mageia 5 => 6 upgrade issues. > > If you haven't seen that this bug got fixed, then please check whether this > bug still exists in Mageia 6. If it does, then please change the Version > (near the top, at the left) to "6". If you know it exists in Cauldron, then > change Version to Cauldron. If you see it in both Cauldron and Mageia 6, > then please set Version to Cauldron and add MGA6TOO on the Whiteboard. > > Thanks, > Marja I don't think this bug exists in mageia 6 (In reply to Sam Khangyi from comment #10) > (In reply to Marja Van Waes from comment #9) > > I don't think this bug exists in mageia 6 Thanks for the feedback, Sam. Closing as OLD Status:
NEW =>
RESOLVED |