I doubt we'll get it down much more, it is easily 1/5 or less than what it used to be. The only way we can cut it back more is to not create multiple streams, which would mean we would have to destroy and recreate the stream view as you switch between the views. Right now it creates all of them and you just slide between them.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/306497 Title: gwibber uses a lot of memory Status in Gwibber: Incomplete Status in “gwibber” package in Ubuntu: Incomplete Bug description: gwibber seems to be using a lot of RAM for being such a simple application. Here's my current "top" output for gwibber: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4662 mkanat 20 0 607m 109m 21m S 0.0 5.5 1:29.76 gwibber As you can see, it's using over 100MB of RES and 607MB in Virt (which is a real mystery to me, though Res is of course what I care about more). I have one Twitter account and one Facebook Status Updates feed configured. It doesn't seem to be leaking memory, it's just always using around 100MB. To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/306497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
