destopcouch memory consumption jumped between 0.6.1 and 0.6.2

The only change I see that looks significant between the 0.6.1 and 0.6.2 tarballs is the import of "dbus" python module. That would consume memory on first usage, but not on subsequent CouchDatabase object instances.

However, if Gwibber is using DBus already, this would not be a difference between the two versions of desktopcouch, since it's already imported.

My plot above is Resident Memory Size relative to the *number of CouchDatabase instances* (not number of records in a database, as my label implies) appended to a list. References are alive and so no CouchDatabase instances are freed.

>>> l = list()
>>> l.append(CouchDatabase("gwibber_messages", create=True)) # and now check RSS
>>> l.append(CouchDatabase("gwibber_messages", create=True)) # and now check RSS
>>> l.append(CouchDatabase("gwibber_messages", create=True)) # and now check RSS
>>> l.append(CouchDatabase("gwibber_messages", create=True)) # and now check RSS
>>> l.append(CouchDatabase("gwibber_messages", create=True)) # and now check RSS
....

Looks like the culprit is the report_changes call in CouchDatabaseBase, in desktopcouch/records/server_base.py

I added a return False at the beginning of that method and the RSS only went up 490K this time and it returned very fast. The same call before was taking over 4 seconds.

This bug was fixed in the package desktopcouch - 0.6.3-0ubuntu2

---------------
desktopcouch (0.6.3-0ubuntu2) lucid; urgency=low

  * debian/patches/lp_534171.patch
    - Don't parse all the _changes feed; work out update_seq from the DB info,
       so we never request the whole feed, which is doom when the whole feed is
       large. (LP: #534171)
 -- Ken VanDine <email address hidden> Mon, 29 Mar 2010 21:24:15 -0400