Bug 428662
| Summary: | memory leaks in XFCE4 (desktop,menu-plugin, sensor-plugin) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | William A. Mahaffey III <wam> | ||||||||
| Component: | xfdesktop | Assignee: | Kevin Fenzi <kevin> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 8 | CC: | christoph.wickert, rayvd, rvandolson | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-01-09 07:55:39 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
William A. Mahaffey III
2008-01-14 14:20:22 UTC
Sorry to hear you are still seeing this. ;( I will see about filing an upstream bug to see if they have any ideas. We may want to try and run valgrind on things, will let you know on that. ok, two things:
1. Do you have the "Launch Gnome services on startup" or the "Launch kde
services on startup" options set? (In sessions and startup -> advanced).
2. Can you try installing valgrind, logging in, then killing xfdesktop and
running it again via:
G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --tool=memcheck \
--leak-check=full --leak-resolution=high --num-callers=50 -v \
--log-file=xfdesktop-valgrind xfdesktop
and then attach the xfdesktop-valgrind log to this bug?
Answers: 1: no & no. 2: This box is a working box for me, it would be unproductive .... I have valgruind installed (valgrind.x86_64, 1:3.2.3-7), use it in my own paltry developement efforts, I'll see if I can get around to it; sorry (in advance) if I can't be more helpful. I noticed this today for the first time. xfdesktop and xfce4-menu-plugin were using up about 600MB's of memory each and were causing my machine to begin swapping. I just restarted XFCE to clear up the issue. Neither GNOME nor KDE services are set to start. I'll post a valgrind log shortly however. I'm running on i386, so I don't think this is necessarily architecture specific. Note that this is with xfdesktop-4.4.2-1.fc8. I have also seen an Ubuntu bug describing the same thing, but haven't yet looked upstream. Created attachment 292560 [details]
valgrind output
Here's my valgrind output. Bout a three hour runtime or so.
Interesting. I do see a report in the ubuntu bug system, but nothing upstream. The valgrind output might be more usefull if you can do: yum install yum-utils debuginfo-install xfdesktop And run the valgrind command from comment #2 again? I will file something upstream. Thanks for the report. I have filed an upstream bug on this: http://bugzilla.xfce.org/show_bug.cgi?id=3812 Created attachment 292574 [details]
Second valgrind run with debuginfo RPM's installed.
Ran it again this time with the debuginfo packages installed. :-) I will send
upstream as well. Thanks!
Looks like Brian upstream has found one leak... I have created a xfdesktop scratch build for F8: http://koji.fedoraproject.org/koji/taskinfo?taskID=483074 Would any of you folks who are seeing the leaks be willing to try that build out and run valgrind/let it run for a few days and see if that the main culprit? Or if there are further ones to find? Created attachment 297263 [details]
valgrind output from xfdesktop-4.4.2-2.fc8
Tried with your scratch build. No valgrind expert, but it does look a lot better? Yeah, it does. William: Can you give it a try and see what your memory leaking looks like? William: Have you had any chance to try out the scratch build from comment #9? I yum-updated 2 XFCE packages (xfce-utils & xfce-mcs-plugins, all I saw available for update @ that time) last week (the 17th) & rebooted. I am observing & will keep you posted .... Ah, no. The updated package here is xfdesktop... see the link in comment #9... I have not yet pushed this as an update, there is only the scratch build in comment #9. Can you update to the xfdesktop there and see if it helps? I guess I can look at pushing an update for it anyhow, as it does appear to fix at least some of the memory leaking issues. Sorry for leaving this hanging so long. I was hoping more leaks would be found. I have pushed the patch we have to rawhide. If it looks ok after a few days, I will look at pushing out to f9/f8. If you folks could test and run valgrind on it after that, that would help us squash any further leaks. Thanks. xfdesktop-4.4.2-4.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/xfdesktop-4.4.2-4.fc9 xfdesktop-4.4.2-2.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/xfdesktop-4.4.2-2.fc8 xfdesktop-4.4.2-2.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xfdesktop'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-8838 xfdesktop-4.4.2-4.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xfdesktop'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-8866 xfdesktop-4.4.2-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. xfdesktop-4.4.2-4.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 WONTFIX if it remains open with a Fedora 'version' of '8'. 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 prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping So, can any of you folks who were seeing the bad leaks still spot any? (any release is fine, f8/f9/f10/rawhide). I haven't had any additional issues (Fedora 8 still). Excellent, and you are using the xfdesktop-4.4.2-2.fc8 version? I think this may have at least plugged the worst of the leaks... Thanks for the feedback! Correct. Thanks much. Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |