gwibber-bugs team mailing list archive
-
gwibber-bugs team
-
Mailing list archive
-
Message #00604
[Bug 735837] Re: Gwibber should prune the messages database
*** This bug is a duplicate of bug 727132 ***
https://bugs.launchpad.net/bugs/727132
** This bug has been marked a duplicate of bug 727132
gwibber.sqlite grows too big and causes gwibber to hang
* You can subscribe to bug 727132 by following this link: https://bugs.launchpad.net/gwibber/+bug/727132/+subscribe
--
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/735837
Title:
Gwibber should prune the messages database
Status in Gwibber:
New
Bug description:
Unless this is a design feature, the Gwibber messages database should
be periodically pruned. I noticed Gwibber was running slower and
slower, until it eventually froze and stopped updating. When I
inspected the Gwibber SQLite database, it was ~200MB in size and had
messages going back to 2009 (when I first started using it I imagine).
I'm not quite sure of the necessity to keep messages that long, but
they certainly don't improve the performance of the application
(especially if it only shows the last 100 or so messages).
I'm running Gwibber 2.91.91.1 (from Natty) on Ubuntu 10.10 (Maverick).
References