Comment 17 for bug 306497

Here's an illustration of the memory behavior of Gwibber on my system. The graph plots resident memory numbers reported by ps against total process time. It represents about two days of running Gwibber on my laptop under normal use and ends with Gwibber using 238,616 KB. Gwibber is the number one process on my system for memory usage (6.5%).

It looks to me like the rate of increase is nearly constant. That might indicate it's not due to an accumulation of messages, which ought to vary over time. Maybe there's some connection resource that's not being released after every refresh?