plasma memory leak

on my main rig, Plasma seems to slowly devour memory. on start-up, its memory usage is around 23MB. As the hours tick by, it ramps up significantly. I’ve been logged into my rig for about 6.5 hours now, and, according to System Monitor, Plasma is now gobbling up 83MB. Also, when the memory usage ramps up, so does CPU usage. The task manager becomes unresponsive, and System Monitor reports Plasma taking up anywhere from 50-95% of my CPU. After, say, 30 seconds of that it goes back down to >5%.

My other system, an Aspire One, is running an otherwise identical software stack (save for the drivers), but I don’t seem to notice the leak that much. Right now, that thing’s been on for about 3 hours, and the RAM usage has gone from it’s initial ~23MB up to 30MB. But, that thing doesn’t see the uptime of my main rig (only wireless network out here. the Aspire’s wifi radio tends to crap out when it gets hot, and I have no use for it without network).

Both systems have the panel along the left edge of the monitor, with (going down) Lancelot, New Device Notifier, Task Manager, Digital Clock, and System Tray. Both have Folderview and Twitter on the desktop. The only differences in Plasma configuration between the two is the main rig has the Comic applet (Aspire does not) and the Aspire has the Battery applet in panel (main rig does not). Removing the comic applet (bringing it in “applet parity” with the little guy) doesn’t bring the memory usage back down.

Both systems are running the KDE4 Factory repos, currently with kde4-workspace-4.2.0-191.4, though I’ve notice the behavior since… whichever build was just before 4.2.0-88.*.

Anyone have any ideas? It seems to be isolated to one of my machines, so I’m not sure if its a bug, or if I just messed something up localy.

Well, all the “information” pop-ups from the “Add Widgets” dialog seems to imply that it’s KDE 4.2.0 “Release 93”.

Looks like the repos have been refreshed, so I’m grabbing the new builds. Guess in a couple hours I’ll see if anything’s changed.

Well, looks like the main culprit was the Twitter widget. There’s still a memory leak somewhere, but it’s not nearly as bad. Memory usage still starts right around 20, but doesn’t make it up to 30 by the time I run “zypper up” and reboot into the fresh build every couple days. In the meantime, guess I’ll stick with Choqok.