SageTV client memory leak?

[hocky98]

Is it normal for the SageTV client to keep using 1M of memory more every second? I just watched the memory usage increase to 360MB from a start of 265MB, after 360MB it increases slowly.

I'm trying to diagnose why the video stutters on recorded playback. It is very strange and requires a server reboot to fix. It seems like a memory leak to me.

I'm using SageTV and client at 5.04.

[nielm]

What is the client doing at this time (playing back video/music/idle)
Which version?

[blade]

Are you running a 1.5. version of java and VMR9? Those versions of java have a known memory leak.

[hocky98]

The client is just playing back a recorded video set to 'best" at 3.0gb/hr on the server.

The client and server are both 5.0.4. version. The server's SageTv.exe stays steady but the client's SageTv.exe runs the memory up to 360K in 1K increments while I watched in taskmanager. Then when it got up to 360K it increases by ~10 bytes. It seems to reach a ceiling but still climbs.

Soon after that, my video stutters. I have to reboot the server. Restarting the SageTv on the server wont do it.

I've yet observed another situation where the client just completely stops playing but was not exited, for about 10 or so minutes, then the video will not stutter after restarting.

There it goes again..video stuttering..

[hocky98]

Originally Posted by blade

Are you running a 1.5. version of java and VMR9? Those versions of java have a known memory leak.

I just went through a marathon install of MCE and back to XP with SageTV. This is a new setup so the only java I have is the 1.4.0_11 version that SageTV installed.

I cannot stand this stuttering. It is reproduceable.

[hocky98]

Well now the stuttering is with live TV..so it doesnt seem to be recorded video related.

[hocky98]

Originally Posted by blade

Are you running a 1.5. version of java and VMR9? Those versions of java have a known memory leak.

Should I downgrade my client PC's java as well to 1.4.0_11? I think Im using 1.5.

[heffe2001]

Since the client is where you're seeing the suttering, I would say downgrade it, or upgrade it to one of the latest 1.6's (that fixed my client machine).

[hocky98]

I just downgraded to version 1.4.0_11 like the server that SageTV installs. Once again I'm watching it climb from 84K start all the way to 360K at 1K increments and then inching up.

I only saw 1.5.0_10 update as the latest. You're using 1.6 beta?

[hocky98]

When I changed the channel, it goes back down to 100K and increases from there. Is this caching it or a java memory leak? (looking at the SageTVClient.exe process).

[hocky98]

SageTVClient climbs to 368,500K and stuttering starts with java 1.4.0_11.

Wow the stuttering recovers after flipping the channel, where SageTVClient resets to 100K and climbs again.

phht..SageTVClient crashed..

[blade]

Originally Posted by hocky98

SageTVClient climbs to 368,500K and stuttering starts with java 1.4.0_11.

Wow the stuttering recovers after flipping the channel, where SageTVClient resets to 100K and climbs again.

You did uninstall the newer versions of java and verify that Sage is using 1.4.0_11?

I get 131,512K usage during playback.

[hocky98]

Heres what I've tested and currently using..

SageTV (server) - at java 1.4.0_11
SageTVClient
- at java 1.5.0_08 - stuttering at 360MB
- at java 1.4.0_11 - stuttering at 367MB
- at java 1.6 RC - stuttering at 367MB

But I may be looking at the wrong thing because all this time my server is at java 1.4.0_11 which came with SageTV 5.04.

I took a risk and uninstalled java and reinstalled 1.6 RC on the server , rebooted, running the same version as my client's, and now I'm watching live TV.

Although the client is at 387,432K (and holding) I have not seen a stutter. I've been watching this one channel for an hour and usually it happens within 20 minutes.

On the server, SageTV.exe is at 108,036K but it seems to hold steadily but I am not quite sure why it grows anyway since it is only streaming.

But with java 1.6 RC on both systems now, it seems to be holding. But, with the small increments on the server, I may end up stuttering after a day.

Yes, I do an uninstall and reinstall of the offline java se package from sun.com. For now it seems from my tests that its the java on the server side that may be causing the stuttering.

[hocky98]

Originally Posted by blade

You did uninstall the newer versions of java and verify that Sage is using 1.4.0_11?

I get 131,512K usage during playback.

Does it hold at that usage or increments?

[blade]

Originally Posted by hocky98

Does it hold at that usage or increments?

It stays at that amount.

If the memory leak is on the client then I would think you should be making changes to the client not the server. I know java 1.5 has memory leaks and I believe some decoders have been known to have leaks. The most common cause is java 1.5, but if that's not your problem I don't have a clue. Maybe someone else has an idea.

[hocky98]

Well,

My memory usage is higher because I did edit the demux registry to allocate 512K and 512 for the other value. Thats why mine is higher and supports my theory that its the cache increasing. The leakage is more controlled now with java 1.6 .

Im at java 1.6 at both sides now and it seems to hold. It did stutter after some 2-3 hrs of viewing which is better than before.

I've also heard that the FusionHDTV card is prone to many IRQ induced stuttering. That is bad because my ATi HDTVWonder is somewhat lesser than that card and I wanted to get two FusionHDTV lite for QAM but this news is bad.

Anyone know if USB tuners are prone to IRQ issues as well?

[ke6guj]

Originally Posted by hocky98

I've also heard that the FusionHDTV card is prone to many IRQ induced stuttering. That is bad because my ATi HDTVWonder is somewhat lesser than that card and I wanted to get two FusionHDTV lite for QAM but this news is bad.

I wasn't aware that you could pull QAM off of a FusionHDTV card in Sage, only in the native software. That only those new external HDTV tuner boxes, such as the Homerun, could do QAM with Sage.

[hocky98]

Originally Posted by ke6guj

I wasn't aware that you could pull QAM off of a FusionHDTV card in Sage, only in the native software. That only those new external HDTV tuner boxes, such as the Homerun, could do QAM with Sage.

Sorry I wasnt specific but I do not know the answer. I suppose Sage cannot.
I was more concerned with the stuttering of using multiple cards. Their dual HD tuner is only for Australian/Eur markets. If I get stuttering, I doubt it'll do QAM well at all. Stuttering just sucks.

[nielm]

Blade: the java 1.5/VMR9 leak is a HANDLE leak, not a memory leak...