testing gwibber on natty with facebook+twitter seems to have improved things. duplicated bugs and comments on this bug tend to refer to huge memory leaks, which i can no longer reproduce in gwibber . memory leak issues may have coincided with the facebook update issues e.g. bug #595265 ? can other affected users confirm that the bug is now resolved?
-- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/306497 Title: gwibber uses a lot of memory Status in Gwibber: In Progress Status in “gwibber” package in Ubuntu: Triaged 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. _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
