Package: python-inotifyx
Version: all
Severity: important
Tags: upstream patch
Dear Maintainer,
* What led up to the situation?
I'm using python-inotifyx to monitor a folder (and subfolders) for new files
and noticed my application continue to grow in memory consumption (starts at
300kb and after an hour it's at 500MB and very slow)
* What exactly did you do (or not do) that was effective (or ineffective)?
* What outcome did you expect instead?
I tracked it down to the inotifyx c-library not decreasing references after it
passes the event on.
the change is simple:
--- inotifyx/binding.c 2011-07-09 20:45:10.000000000 +0000
+++ inotifyx/binding.c.new 2014-04-09 12:11:01.597888661 +0000
@@ -194,6 +194,7 @@
if(PyList_Append(retvalue, value) == -1) {
return NULL;
}
+ Py_DECREF(value);
i += EVENT_SIZE + event->len;
}
* What was the outcome of this action?
I've run this in production for months without memory growth or other issues.
(application stays at <2MB memory usage)
I've created a ticket on the projects launchpad page, but haven't received
response for about a year so i guess the original maintainer has lost interest.
-- System Information:
Debian Release: 7.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8.13-999-generic (SMP w/32 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
