Bug 1437159

Summary: xfce4-wavelan-plugin-0.6.0-1.fc25.x86_64 leaks memory
Product: [Fedora] Fedora Reporter: Artem S. Tashkinov <aros>
Component: xfce4-wavelan-pluginAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-27 21:05:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artem S. Tashkinov 2017-03-29 16:29:51 UTC
Nothing to add really.

On startup eats roughly 23MB (RSS), after 8 hours increases to 56MB of RAM.

That makes it 99MB a day which quite a lot.




P.S.

Debian confirms:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698310

Ubuntu confirms:

https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1534963

Comment 1 Mukundan Ragavan 2017-04-07 00:24:59 UTC
Can you file this upstream or would you prefer that I do?

There is a recent release of xfce4-sensors-plugin that has a bunch of memory fixes. This could be a similar fix ... may be.

Comment 2 Artem S. Tashkinov 2017-04-07 07:11:15 UTC
(In reply to Mukundan Ragavan from comment #1)
> would you prefer that I do?

This.

Thank you!

Comment 3 Artem S. Tashkinov 2017-04-07 07:14:13 UTC
Apparently Ubuntu does not confirm - it's a different applet. Sorry for the misinformation.

Comment 4 Fedora End Of Life 2017-11-16 19:50:16 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Ben Cotton 2018-11-27 18:12:51 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Artem S. Tashkinov 2018-11-27 21:05:17 UTC
Let's hope upstream will someday solve this issue.