Hello all!
I'm running two instances RL 2.5.0.1 on a WinXP system, loads of memory and horse power. (XP runs two instances without issues, Win7, not so much)
We are recording AAC streams:
http://ckkq.streamon.fm/listen.m3u and http://cjzn.streamon.fm/listen.m3u
Recorded audio samples can be found here:
https://drive.google.com/folderview?id=0B94OYQ9j4V3ZVVh4NHBIRUhoWmM&usp=sharing
The software starts up and runs fine for the first 24 to 48 hours with good recordings, normal CPU and memory usage. (Around 1% CPU and 16,000K Memory per instance and each recorded file around 21MB).
After 24 to 48 hours, the CPU and memory usage will jump, but recordings will continue as normal. (Aprox 25% CPU and 285,000K Memory per instance)
Another 24 to 48 hours and the recordings begin to skip as well as the recorded file sizes reduce to half normal size, around 9.5MB.
Closing the programs and restarting them (not the system) corrects the problem temporarily, but it returns after 24 to 48 hours.
The screen shot of the task manager below shows where the CPU and memory usage settle back down after restarting the program.
I'm running two instances RL 2.5.0.1 on a WinXP system, loads of memory and horse power. (XP runs two instances without issues, Win7, not so much)
We are recording AAC streams:
http://ckkq.streamon.fm/listen.m3u and http://cjzn.streamon.fm/listen.m3u
Recorded audio samples can be found here:
https://drive.google.com/folderview?id=0B94OYQ9j4V3ZVVh4NHBIRUhoWmM&usp=sharing
The software starts up and runs fine for the first 24 to 48 hours with good recordings, normal CPU and memory usage. (Around 1% CPU and 16,000K Memory per instance and each recorded file around 21MB).

After 24 to 48 hours, the CPU and memory usage will jump, but recordings will continue as normal. (Aprox 25% CPU and 285,000K Memory per instance)

Another 24 to 48 hours and the recordings begin to skip as well as the recorded file sizes reduce to half normal size, around 9.5MB.
Closing the programs and restarting them (not the system) corrects the problem temporarily, but it returns after 24 to 48 hours.
The screen shot of the task manager below shows where the CPU and memory usage settle back down after restarting the program.
