Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
Hey, i just sound some kind of bug, well miau, found it, we were doing a ftm with many tracks, and it's seen like famitracker just overload the ram something, cuz it's goes high... here is an screenshot... (check the attatch).
Jsr i will send you the *.ftm on private because i dont wanna share the source, atleast not yet.
Holy massive memory leaks, Batman! o_O I think I'm going to take a look at the RAM usage of FT with my multi-track FTM; hang on…
…also, quick question: I'm assuming that you're running 64-bit XP/Vista, so the '*32' things at the right of some executable files' names denotes that they're 32-bit, right? >.>? Sorry for this being off-topic, I've just only used 32-bit operating systems, so I'm not entirely sure if the '*32' is what I think it is or not.
Edit: hm, my multi-track FTM has a couple more tracks than yours does, and has possibly two times the amount of instruments, yet it only takes about 11,000K of my 256MB of RAM (yes, I know I have hardly any). o.O The FTM file itself is only about 48KB.
kizul, for personals reason i cant post the ftm, at least not yet. I will share it them. But yeah i'm using vista 64 bits, but miau got the same problem and he use an OS of 32 bits
My ftm is about 60KB, it have 21 instruments the only strange i made with this FTM, is open it in different computers and save the file many times, copy paste pattern from famitracker to famtracker, i mean... maybe some lost data is doing somthing with the ram to overload it?. I really dont knwo what can be ... miau and me just noticed that on the FTM, i already sended the ftm to jsr. But dont know if he get it.
This was a problem that's now fixed in the new WIP. As the tracker only supported one track first, there was no memory optimizations to decrease memory usage. And I never checked how much memory each track actually required, so the problem became obvious when using many tracks.
But it works better now after some optimizations (like, parts of tracks are only allocated when used).
jsr ok ok :X good to know that... i still using the 0.27 and eventually 0.26 XD... but when the 0.28 get out i'm sure i will jump to that version. I tested the vcr6 and it works "perfect", i know still need a lot of optimization, etc... but works fine. I hope keep in my some of my ideas to make the tracker even better to compose :P. And as i told you before, if you need anything, let me know on irc or email me....