Memory Leaks -> Lockup?

[nielm]

Not sure how long this was going on for me either: I only noticed it when checking for mem leaks...

Narflex: I am just gathering some more info, checking it occurs on both my systems under what conditions and I will of course submit a bug report...

[stevech]

So a handle is a reference to an object, eh? A window element, a file, a process, etc. An failure to release an unused handle is a form of memory leak, it seems, just one level removed from, say, malloc() without free()

[nielm]

I have updated my CPU/Mobo monitor to add handle monitoring

For me it definately leaks 2 handles/frame on playback (50 handles /sec as I am in PAL land), for both XVID/AVI and MPEG2, but only when using VMR9.

[bcjenkins]

Has anyone made any progress with a bug report on this? I filed one yesterday, no response yet. The system crashes in about 12 hours if live TV is left playing. I am 9 hours into it from the last crash, 2.4MM handles and close to 200MB memory. When it reaches 225, I expect it to crash.

B

[Narflex]

The handle leak is a confirmed bug in Java 1.5/1.6. We'll be redoing some things to get around the problem.

[HawgGuy]

FWIW I have the same problem. Exit to the Desktop 12-24 hrs after starting. Only with VMR not with Overlay. I much prefer VMR.

Same results:
Win2k or WinXP
Sage, Cyberlink or Nvidia codec

SageTV 4.13 --> 5.02 (all versions) - stock, no "enhancements"
Nvidia 6600 or Nvida 5200 video card
Java 1.5.06

I'm growing more suspicious of the Nvidia drivers. My next step is to get a cheap ATI card to test with their drivers.

-bob

[stevech]

how do I determine which version of Java (VM?) I am using (Sage 4)

[Opus4]

Among other things, it should be displayed as the 2nd line on SageTV's System Information screen. That's the one SageTV is using.

- Andy

[nielm]

...And just to (re) confirm that the problem does not occur in Java 1.4 (I am now running 1.4.2-11) Sage is stable at 832 handles, going to 976 during video playback...

VMR9 is also a lot more stable when switching to/from full screen exclusive mode... So I will stick with 1.4 for the moment (which is a pain because a plugin I am working on will require 1.5 unless I rewrite large sections of a 3rd party library!... Damn!)

[HawgGuy]

I dropped down to JRE 1.4.11 and also have noticed my number of handles had decreased from 800,000 (and climbing) to a stable 5800 or so. Only time will tell.

[stevech]

My seemingly handle- and memory-leaky SageTV uses Java 1.4

[DFA]

1.4.?

I have been following this thread closely. These are the type of ghosties that raise real havoc that you just can't quite put your finger on. It looks like this one is exposed.

DFA

[thorhtpc]

I have been running the SageTV trial software for the last few days. I was unable to use VMR (with or without FSE) without a lot of video jitter. I could only use overlay to get smooth playback.

Seeing that people were having problems with java 1.5 in this thread I decided to uninstall 1.5 and go back to 1.4.

I am happy to say that I have no more problems using VMR. There are definitely problems with java 1.5.

[stevech]

What is Sage's Position on Java 1.5???

Does upgrading to Sage v5 automatically load Java 1.5?

[Opus4]

No, the java that is in the installer only gets installed if you don't have a version of java installed already.

- Andy

[stevech]

"a version" ? Does installer push in a newer version based on JVM version of what's installed?
Often the Installers in general don't ask.

[elaw]

Hmmm... maybe this explains why I had to restart Sage 6 times to get through watching "The Langoliers" last night?

Anyhow since I've got two HTPC's I decided to do a little experimenting. The one I was watching last night definitely DOES have a handle leak. This machine has Sage 5.0.2 and had Java version 1.4.2.

I quickly figured out it only has the problem when viewing .avi files that use Divx or Xvid, .mpg files (including Sage recorded shows) do not have the problem.

I tried changing a bunch of settings: video and audio renderers, fullscreen/not, etc., with no luck. Hitting "reload media player" in Setup does not free the handles.

So I moved on to my other machine, this one running same version of Sage but Java version 1.5.0. Quickly figured out that machine does NOT have the handle problem.

So thinking I'm really smart, I go back to the first machine and install the newer version of Java on it. Did NOT work, that machine still has the problem (yes I rebooted and verified that Sage is using the new Java version).

Biggest remaining difference between the machines is #1 has nVidia 6600 video and #2 has ATI 9500. Wonder if the problem could lie with the nVidia drivers?

[Narflex]

This is a confirmed bug in Java that we're developing a workaround for (shouldn't take that long). It only happens when using VMR9 with Java 1.5 or 1.6. There are also other ways to make it leak handles when not using VMR9, and those will be addressed as well (but they're all related to the same bug in Java, but the non-VMR9 leaks are not as bad).

[mike1961]

FWIW - I noticed that (as I posted earlier) when I select VMR I get the handle leak but not when I select either Overlay or Default. Also, I noticed that in the latest version 5.0.2 that selecting VMR uses like 60-90% of my CPU resources while Overlay only uses like 10% of my resources. Overlay or default seems to work just fine for me.

Mike

[toricred]

I tried JRE 1.4.2_10 today and it was much worse. Every 1-2 hours it would totally lock up. I've reverted to Sage 4.1.14 for the time being. There's nothing I'm really interested in in version 5.