Bug 117308 - Gamin leaks memory.
Summary: Gamin leaks memory.
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Andreas Jaeger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-15 18:50 UTC by Robert Love
Modified: 2005-09-20 12:38 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Love 2005-09-15 18:50:40 UTC 
Gamin 0.1.4 and 0.1.5 contains a memory leak that leaks the control block of
every watch.  On a normal, static desktop this amounts to a very small leak. 
But a highly dynamic desktop can leak hundreds of megabytes a day.

This is fixed in 0.1.6, which also fixes some other inotify-related issues.
Comment 1 Stanislav Brabec 2005-09-16 12:26:28 UTC 
Andreas. How this should be fixed?

Should I try to isolate memleak and fix only it or try to backport inotify
fixes, too, or even update?

http://www.gnome.org/~veillard/gamin/news.html
Comment 2 Robert Love 2005-09-16 13:19:06 UTC 
There are not significant changes in 0.1.6 other than the memory leak and the
inotify updates, so wholesale move to 0.1.6 would not hurt.

I built 0.1.6 packages and they work fine.

aj's call, of course ..
Comment 3 Andreas Jaeger 2005-09-19 07:17:54 UTC 
If I read "Large revamp" and "Code reorganization: Let's stay with the current
release and just fix this one bug. 

swampid is: Maintenance-Tracker-2332, send to Gary.
Comment 4 Gary Ekker 2005-09-19 16:29:09 UTC 
The patch has been submitted.
Comment 5 JP Rosevear 2005-09-20 12:17:33 UTC 
Moving to aj so he can make sure the update is pushed and can close when it is.
Comment 6 Andreas Jaeger 2005-09-20 12:38:24 UTC 
If the patch and patchinfo are submitted, then we can close it.  No need for me
to do anything else.