Bug 182900

Summary:	Twitter widget leaks memory
Product:	[Unmaintained] plasma4	Reporter:	Lars Ivar Igesund <larsivar>
Component:	widget-microblogging	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aseigo, joekowalski, karaluh, kde, kde, ungethym, zejn
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Lars Ivar Igesund 2009-02-02 18:24:57 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

The other day I noticed that my plasma process was using a lot of memory (the machine had slowed down, so I opened top to see if there was anything obvious). plasma did at that point show 370m in the RES column. At this point it was 2-3 days since I upgraded and started the computer with 4.2. 

I restarted everything, followed the progress in top and 10 hours later plasma was using 125m (as shown in the RES column). Since twitter was the only non-essential widget I was using, I shut it down, and now, a day later, plasma's RES is still 125m. I consider this "proof" for the twitter widget leaking fairly substantial amounts of memory.

Comment 1 James Ots 2009-02-03 11:21:56 UTC

I am also finding the same behaviour on the latest 4.2 builds from openSUSE. Plasma starts out using around 20Mb and a day or so later it's at over 100Mb. But only when I'm using the twitter plasmoid.

Comment 2 Nic Gould 2009-02-08 12:56:33 UTC

I can confirm the same behaviour, using openSUSE 11.1 with the FACTORY 4.2 packages on an hp 2133. With the twitter plasmoid on the desktop plasma memory usage grows from an initial 19 M to over 100 M at which point plasma becomes so slow it's unusable.

Comment 3 Joe Kowalski 2009-02-13 16:21:59 UTC

I am seeing this too. After  running a couple of days, plasma hits 350+ megs of memory. After removing the microblogging widget and restarting plasma, plasma is coming in at ~50 megs.

Comment 4 Artur Souza (MoRpHeUz) 2009-02-25 02:58:43 UTC

Hmm...just tested twitter plasmoid with plasmoidviewer + valgrind and I didn't see any serious memory leak. Maybe it's a problem at some other place that gets worse when using twitter plasmoid inside plasma ?

Comment 5 karaluh 2009-02-26 11:43:50 UTC

https://bugs.kde.org/show_bug.cgi?id=184394 might be duplicate

Comment 6 karaluh 2009-02-27 08:01:14 UTC

Do any of you use analog clock, or has digital clock configured to show seconds?

Comment 7 Thomas Thym 2009-03-04 13:42:48 UTC

I can confirm that memory usage of plasma is rising on my system, too. (OpenSUSE 11.0 with KDE 4.2 from Factory-Repo). But I don't use the twitter plasmoid. I have this behavior only from time to time. When I have it the seconds of my analog and binary clock start to jump irregular (bug 186013).

Comment 8 Aaron J. Seigo 2009-04-26 04:42:40 UTC

the twitter leaks have been fixed.

Comment 9 Dario Andres 2009-06-21 01:05:39 UTC

*** Bug 197263 has been marked as a duplicate of this bug. ***