After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640842 - Add memory-leaking tests for common operations
Add memory-leaking tests for common operations
Status: RESOLVED OBSOLETE
Product: folks
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: Unset
Assigned To: folks-maint
folks-maint
Depends on:
Blocks:
 
 
Reported: 2011-01-28 17:43 UTC by Travis Reitter
Modified: 2018-08-04 08:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Travis Reitter 2011-01-28 17:43:25 UTC 
As we saw in bug 640551 and bug 640554, small memory leaks over time can be more serious problems for users who switch networks frequently and rarely reboot.

I didn't notice this since it doesn't fit my usage profile.

Valgrind ships with libraries to track memory leaks. We should wrap this with some convenient Vala functions and make tests to track 'definitely lost' memory for common operations such as:

* account(s) going online -> offline -> online repeatedly (Tp backend)
* Personas getting linked together (general Folks)
* Personas getting anti-linked/split (general Folks)
* avatars changing (general Folks and Tp backend)

We could extend this list even farther, but these seem like some good major cases.

If at all possible, these tests should be part of the regular 'make check' and require that memory 'definitely lost' be zero bytes.
Comment 1 Guillaume Desmottes 2011-03-21 13:47:45 UTC 
I noticed that TpAccount objects are not destroyed when exiting Empathy. As Folks is doing a lot of ref/unref on those, I'd be interested to know if it leaks TpAccount.
Comment 2 GNOME Infrastructure Team 2018-08-04 08:25:05 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/folks/issues/9.