Your message dated Wed, 4 Nov 2015 20:34:24 +1100 with message-id <[email protected]> and subject line Re: Bug#608480: Memory leak in _mysql_ConnectionObject_Initialize has caused the Debian Bug report #608480, regarding Memory leak in _mysql_ConnectionObject_Initialize to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 608480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608480 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python-mysqldb Version: 1.2.2-7 Severity: important Hello, after a (long) database failure I realized that my application used a lot of memory. After some debugging it was possible to reproduce the problem with the following code snippet. from MySQLdb import Connection while True: try: conn = Connection(host='127.0.0.1', user='root', passwd='') except Exception: pass The leak is caused by a resource not deallocated if a Exception happens. This leak is already solved in the 'upstream' repository http://mysql-python.svn.sourceforge.net/viewvc/mysql-python/branches/MySQLdb-1.2/MySQLdb/_mysql.c?r1=625&r2=630 I was wondering if it is possible to include that particular change into the python-mysql version of debian ?? -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 2.6.27.48-0.2-default (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---Version: 1.2.3-1 On Fri, Dec 31, 2010 at 10:05:07AM +0000, Stephan Hofmockel wrote: > This leak is already solved in the 'upstream' repository > http://mysql-python.svn.sourceforge.net/viewvc/mysql-python/branches/MySQLdb-1.2/MySQLdb/_mysql.c?r1=625&r2=630 I am assuming you mean this was fixed in r630. http://sourceforge.net/p/mysql-python/svn/630/tree//branches/MySQLdb-1.2/MySQLdb/_mysql.c?diff=5059d1f5bfc09e26e1a66617:629 ... Meaning this bug would have been fixed in 1.2.3-1. Closing. -- Brian May <[email protected]>
--- End Message ---
_______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
