Summary: | the power management service causes xorg to leak memory | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Andrew <shweduke> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | cfeck, lamarque |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Andrew
2011-11-06 14:55:23 UTC
*** This bug has been marked as a duplicate of bug 271934 *** It is possible this is not really a duplicate, because this one is about xorg, while the duplicate is about kded4 process. By the description in the forum it really looks like a duplicate of #271934 and maybe #281509. #271934 is caused by Policy-qt, which Powerdevil relies on to execute privileged calls. Everytime Powerdevil changes the screen's brightness it executes policy-qt's calls, which leak memory and make kded4 memory usage to grow. I really do not see how Powerdevil could cause Xorg memory to grow. I have noticed the knotify4 memory problem long ago, but I have not had time to debug it and have forgotten about it :-) I'm not really familiar with KDE architecture enough, but if some KDE libraries get loaded into an address space of xorg, it might cause a leak. I also noticed that CPU temp is higher with Power Management enabled than without it. So it looks like it wastes more power than saves :) (In reply to comment #5) > I'm not really familiar with KDE architecture enough, but if some KDE libraries > get loaded into an address space of xorg, it might cause a leak. That is the point, it is very unlikely Powerdevil can access xorg's address space. That would be a great security risk since Xorg run as root. I think the temperature being higher with Powerdevil running is just an impression. CPU temperature oscilates with any minimum difference in the cpu load. |