Comment 10 for bug 306497

WebKit is largely responsible for Gwibber's excessive memory consumption right now. The problem is that the default caching behavior used in the GTK+ WebKit port is intended for web browsers and not applications like Gwibber. This is a problem that needs to be addressed upstream. The relevant bug to follow there is this one: https://bugs.webkit.org/show_bug.cgi?id=24001 I'm going to experiment with some of the patches attached to that bug. If those fixes significantly improve Gwibber's memory footprint, I'm going to talk to some people and see if we can get them applied sooner rather than later.

I'm tackling other resource consumption problems, too. The JavaScript method used to push messages into the content area in trunk is really ridiculously processor intensive. The new template-theme-engine branch almost entirely eliminates that problem.