Bug 192190

Summary: memory leak in plasma/Xorg
Product: [Unmaintained] plasma4 Reporter: Bayley Green <yamikuronue>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bayley Green 2009-05-10 03:44:10 UTC 
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Upon first starting plasma it takes 20mb of ram. Within an hour that's shot up to 38; when I closed it before this experiment it was using 1.9 gb. Xorg also is using over a gig, and I've seen bug reports elsewhere claiming that plasma leaks lead to Xorg leaks. I highly suspect this to be what's causing kernal dumps every few hours seemingly at random, but I don't know how to confirm that since without plasma running it's pretty hard to maintain normal computer use.
Comment 1 Bayley Green 2009-05-10 03:45:38 UTC 
Oh, right, I meant to add - I'm running Jaunty Jackalope, and this is a new issue since upgrading from Intrepid. Ever since upgrading, it's been sluggish and unresponsive as though out of memory.
Comment 2 Aaron J. Seigo 2009-05-10 04:04:31 UTC 
try removing the digital clock from the panel and see if that resolves it for you. also, knowing what x.org video driver you are using might prove helpful

*** This bug has been marked as a duplicate of bug 183191 ***
Comment 3 Bayley Green 2009-05-12 20:13:05 UTC 
Removing the digital clock didn't help. A test using a new user account could only replicate the problem once I added the Twitter widget; clocks made no difference. By setting the Twitter widget to update once a minute, which is how I'd had it, it causes xorg to jump over 100M each update, and only gives it time to release about 4M tops before it updates again. Plasma also seems to be raising in memory usage, but slower. 

I did manage to replicate the clock bug by turning on seconds, but I don't normally use seconds, so that wasn't the issue I was having.
Comment 4 Aaron J. Seigo 2009-05-12 20:26:14 UTC 
a huge number of rather horrible twitter leaks were identified and fixed for 4.3 .. i assume you're using a 4.2.x version?
Comment 5 Bayley Green 2009-05-12 20:27:30 UTC 
It seems so. Thanks.