PDA

View Full Version : 1.4.5: Using 286MB of RAM

salsbst
07-20-2003, 10:34 AM
I have what seems to be a crippling memory leak with 1.4.5.

Symptoms:

* navigating the guide begins to become very sluggish
* eventually, the application barely responds at all. reactions to button presses begin to take minutes
* also, maybe related, I'm seeing intermittent video stutters.

Right now, SageTV is asleep using 286MB of RAM.

The pattern is as follows: as SageTV loads, it slowly clims to around 40,000KB of RAM while the splash screen is visible. Right after the Home screen shows up, memory starts to jump in increments that seem to be of about 5MB each. It eventually reaches 294,000KB, then drops back to 286,000KB, then bounces back and forth between those two for a while, then settles at 286,000KB. All without me touching a button.

I was previously using 1.4.3 without this problem.

I've attached sagetv_0.txt

Regards,
Stuart
Narflex
07-20-2003, 01:56 PM
Try setting:
scheduler/disable_phase1_optimization=false
in the Sage.properties file.

Let me know if that fixes it. If it doesn't, email your Sage.properties and Wiz.bin files to support@freytechnologies.com so I can take a look at them.

Thanks,
salsbst
07-20-2003, 02:03 PM
That seems to have done the trick! It now jumps up 5.5MB only twice after hovering at 40, leaving me at nearly 51MB. Guide is much snappier. I can't actually test if this fixed the video hiccups b/c the GF is watching TV the old fashioned way right now and VNC doesn't see video, but hopefully this will have been corrected, too.

Who would have know that phase1_optimization was so critical? Certainly not me, who doesn't even know what phase1_optimization is.... but I know I like it.

Thanks for your quick response.
salsbst
07-20-2003, 02:18 PM
OK, now that I've found the post that discusses this option ( http://www.freytechnologies.com/forums/showthread.php?s=&threadid=993 ) I guess that phase1 optimization exposed a bug on my machine? I hope so, b/c in the long run I would prefer favorites management to work the way that it supposedly does with phase1 optimization = false.

In the meantime, obviously, [50MB and functional] is a lot better than [280+ MB and extremely sluggish].

Regards,
Stuart