Re: [fluid-dev] Memory problems fixed

2006-11-28 Thread Josh Green
Hello Paul, On Tue, 2006-11-28 at 19:38 +, Paul Millar wrote: > Hi all, > > I'm still having problems (with CVS HEAD) with memory not being freed. This > seems to have been caused by still-active voices maintaining their lock on > the sfont's refcount (see start of delete_fluid_defsfont()

[fluid-dev] Memory problems fixed

2006-11-28 Thread Paul Millar
Hi all, I'm still having problems (with CVS HEAD) with memory not being freed. This seems to have been caused by still-active voices maintaining their lock on the sfont's refcount (see start of delete_fluid_defsfont() in src/fluid_defsfont.c). The solution I've attached is to explicitly call

Re: [fluid-dev] A question of memory

2006-11-28 Thread Josh Green
Sounds like pretty good arguments/information to me. I think it might be better to implement streaming support though, which has been on the wish list for a while. I agree it is a bit overkill to lock all sample data, as it currently is, when possibly only a few are being actually used for the ac

Re: [fluid-dev] A question of memory

2006-11-28 Thread Dave Serls
I've been having an enlightening offline discussion with P. Millar about memory usage within fluidsynth, particularly the 'mlocking' of soundfont sample data areas. I've done some cursory exploration of the source code and come to the conclusion that the hypothetical average user (of which there a