From mths.f...@googlemail.com on October 04, 2012 16:49:03
Hey Jeffos and Fingers,
I tested all of the newly added stuff so far but did spot one thing about SNM_DeleteObject() that is yet a bit unclear to me.
for i in range(10000):
my mem is constantly increasing by a amount, but in fact independent of the last line.
Using Fingers FNG_FreeMidiTake() after FNG_AllocMidiTake() does make a huge difference btw.
PS, it will probably be a bit quite on my side over the next 6 months (studies trouble), so sorry already if i cant contribute with much feedback :/
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=520
The text was updated successfully, but these errors were encountered:
From jeffos...@gmail.com on October 04, 2012 12:05:36
DANG! This one stinks. Many thanks for the report Veto!!
Fixed for the next build ( r896 ), SNM_DeleteObject will be replaced with a new func SNM_DeleteFastString
(.. and I hope your "troubles" won't long too much ;-)
From fingersmcgarnickle on October 10, 2012 12:33:49
Hey, glad it is of some use. You must run FNG_FreeMidiTake() after FNG_AllocMidiTake as you will leak memory and your changes will not be applied to the midi take. I have some wrapper code around using the midi stuff, to make it more safe, but I need to add a few things and append it to the main python module in the build.
From mths.f...@googlemail.com on October 11, 2012 11:03:54
Sorry Fingers, i think i caused some misunderstanding due to my english ""skills"".
sry again for the confusion.
But that beeing done automatically without user-interaction (if i understand you right) would be pretty cool too.