[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-freedink] Bug#748090: freedink-engine: leaks lots of memory, render
From: |
beuc |
Subject: |
[Bug-freedink] Bug#748090: freedink-engine: leaks lots of memory, rendering system unresponsive |
Date: |
Wed, 14 May 2014 11:44:33 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi,
On Wed, May 14, 2014 at 12:41:58AM -0700, Ben Longbons wrote:
> Package: freedink-engine
> Version: 1.08.20120427-2.1+b1
> Severity: important
>
> Dear Maintainer,
>
> After running freedink for a while, it allocates several gigabytes of
> memory, which makes the system unresponsive due to lots of swapping.
>
> The problem is particularly noticable in the Edge of the World when
> walking between the church and the dangerous parts to the left.
>
> It leaks over 100 MB each time.
>
> valgrind gives a bunch of different backtraces from libfluidsynth.so,
> but they all come from the same part of freedink:
Can you check if you have the same behavior with the traditional
TiMidity backend?
I think you can force it with:
SDL_FORCE_SOUNDFONTS=1 freedink ...
You should hear a noticeable difference in the music - and possibly a
difference in matter of RAM usage ;)
If no leak, this means the leak comes from the new fluidsynth backend
in libsdl-mixer.
Cheers!
Sylvain