Your message dated Sat, 23 May 2009 16:57:26 +0300
with message-id <[email protected]>
and subject line Re: Is bug 462837 present in later versions?
has caused the Debian Bug report #462837,
regarding fluidsynth: heavy memory leaks
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.)
--
462837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462837
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libfluidsynth1
Version: 1.0.7a-1
Severity: normal
Tags: fixed-upstream
Hello,
Fluidsynth 1.0.7 leaks memory quite heavily (depending on the soundfonts
size, I guess) when it is initialized and deinitialized multiple times
from within the same process.
It would seem that upstream version 1.0.8 fixes this issue.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (100, 'unstable'), (100, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.23.14 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libfluidsynth1 depends on:
ii ladcca2 0.4.0-6 LADCCA shared library files
ii libasound2 1.0.15-3 ALSA library
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libjack0.100.0-0 0.109.0-1 JACK Audio Connection Kit (librari
ii libncurses5 5.6+20080119-1 Shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii libuuid1 1.40.4-1 universally unique id library
libfluidsynth1 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Le Saturday 23 May 2009 07:42:42 David Henningsson, vous avez écrit :
> Could you please try 1.0.8 or 1.0.9 too see if the problem is actually
> fixed or whether it persists? Thank you!
It seems gone. Thanks.
--
Rémi Denis-Courmont
http://www.remlab.net/
--- End Message ---
