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 309079 - Memory leaks when syncing PDA on FC4
Memory leaks when syncing PDA on FC4
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: general
1.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-06-26 19:42 UTC by Mark Adams
Modified: 2005-07-02 08:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Fix leaking of uid strings. (273 bytes, patch)
2005-06-26 19:43 UTC, Mark Adams 		none Details | Review
Fix object leak (427 bytes, patch)
2005-06-26 19:43 UTC, Mark Adams 		none Details | Review

Description Mark Adams 2005-06-26 19:42:31 UTC 
Distribution/Version: Fedora Core 4

While debugging the syncing mess on FC4 as described in bug #274032 I found some
memory leaks in the evolution data server when running under valgrind.

The attached patches fix the two memory leaks I encountered to date.
Comment 1 Mark Adams 2005-06-26 19:43:11 UTC 
Created attachment 48376 [details] [review]
Fix leaking of uid strings.
Comment 2 Mark Adams 2005-06-26 19:43:52 UTC 
Created attachment 48377 [details] [review]
Fix object leak
Comment 3 André Klapper 2005-06-26 22:17:49 UTC 
adding perf and patch keyword.

please also post patches to evolution-patches mailing list (see 
http://lists.ximian.com/mailman/listinfo/evolution-patches) and please include a 
changelog (see http://www.gnome.org/projects/evolution/patch.shtml
for more information).

thanks in advance! :-)
Comment 4 Mark Adams 2005-06-27 15:01:50 UTC 
Not a problem. Posted:
http://galactus.ximian.com/pipermail/evolution-patches/2005-June/011002.html
Comment 5 Harish Krishnaswamy 2005-07-02 08:24:39 UTC 
The patch does not fix the underlying problem correctly. A different fix has been
committed. Kindly look into patches list for details.