I was testing my first schedule tonight. Here is what happened.
Ok first off - I thought I had 512MB, but my kids keep stealing my memory and putting it in their machine. So right now I only have 256MB. That will change soon.
The schedule starts out great - runs fine. Memory use on my machine was at about 230MB with Vixen running. But as time goes on, my memory use goes up, and up and up. I decided to stop the schedule when it reached 900MB comitted. Poor little hard drive was caching like crazy and my limit is set to just over 1Gig.
The schedule started at 6:30 and I stopped it after the football game at about 9:00, So it took about 2 1/2 hours to happen.
Can we take a look at then memory usage - I think that there is a memory leak somewhere. The longer you run the more memory is used up.
As soon as I closed Vixen - it went back to normal, about 210mb in use.
This may be causing some of these other problems too.
Thanks for the head's up on this.
Not sure if this is any help KC. Slush did you have the music player running in vixen. There is a memory leak in it. If watch your avaliable memory in task manager while the music player is running you will notice that each time a new song or mp3 clip is run it loses about 800K so over a few hours it will really eat up the memory. My system has 1 gb of ram and with nothing but vixen running it will lock up vixen after about 10 hours of the music player going. If I stop vixen before this happens it will return all the memory back to the O/S. Just a thought on this. Hope it helps in some way.
RJ
I was running a program with 3 sequences with a runtime of 5:39.
All of them have music.
When I closed Vixen, it did release the memory.
I wonder if this memory leak is the reason for the music skipping.
I don't notice the music skipping it just use more memory at the start of each song.
so is there a way around this or an easy fix, or is this something that KC has to do in the program?
This is a K.C. kinda fix.
There was one glaring memory leak in the music player that is addressed in the next update, so we'll see how it behaves after that. I'm still having an issue specific to WMA files, but it seems to be localized to me.
Tonight I ran my sequence with a different profile. I removed the adjustable preview from it.
The memory leak was gone. I ran all night with no extra memory used.
