100% CPU usage with SageTVService.exe

[matt91]

Since installing the v6 beta, I regularly experience situations where my CPU usage is 100% (all of it's sagetvservice.exe) even without doing anything on the server.

My server is headless, and does nothing but run sagetv in service mode. I connect 2 MVP to this server....and that's my whole setup.

Once i stop/restart the service (via remote access), all works fine -- for half a day or so.

I'd like to file a bug report, but I'm not sure what to include. Is there a way to dump my CPU usage (over time) to a file? I'm not sure when it spikes to 100%, just that it does.

I've watched it stay at 100% for 20min or so, so i don't think it's coming back down on its own.

thanks

matt

PS I guess it goes without saying, but my server ran v5 for weeks or months without a hiccup (or restart ). No new software other than v6.

[srothwell]

Originally Posted by matt91

Since installing the v6 beta, I regularly experience situations where my CPU usage is 100% (all of it's sagetvservice.exe) even without doing anything on the server.

My server is headless, and does nothing but run sagetv in service mode. I connect 2 MVP to this server....and that's my whole setup.

Once i stop/restart the service (via remote access), all works fine -- for half a day or so.

I'd like to file a bug report, but I'm not sure what to include. Is there a way to dump my CPU usage (over time) to a file? I'm not sure when it spikes to 100%, just that it does.

I've watched it stay at 100% for 20min or so, so i don't think it's coming back down on its own.

thanks

matt

PS I guess it goes without saying, but my server ran v5 for weeks or months without a hiccup (or restart ). No new software other than v6.

If you're using the malore menus in the unsupported extras, turn them off. There's a bug that causes this CPU usage. It's supposed to be fixed in the next beta.

[matt91]

ok, i set "enable malore custom menus" to 'no' in the customize section.

we'll see what happens!

thanks for the tip - i hadn't read about it.

Matt

[Opus4]

If it is because of those menus, there is an updated STV to try here. If the 100% cpu usage is happening when neither MVP is on one of the malore style 2-pane menus, then it is a different issue.

- Andy

[matt91]

While it seems to be very similiar, I'm not sure this is my problem.

I disabled the extras completely, but sage still happily chuggs away at 100%.

Back to my original question - any way to track the cpu usage? Gets tiring watching the graph cycle up and down for 20 minutes!

I'll monitor it w/o any MVPs running and see what happens. My hunch is that at some point it will spike again.

Matt

edit: Well, maybe I'm wrong. I've been running the server for 20min with no MVPs, and then 20min with a MVP, and I'm at 2%. Perhaps it was the problem after all.

[Goodspike]

Originally Posted by matt91

Since installing the v6 beta, I regularly experience situations where my CPU usage is 100% (all of it's sagetvservice.exe) even without doing anything on the server..

Are you sure it's not Sagetvtranscoder? A few other people and me have reported that portion of the program using up CPU cycles.

[matt91]

Yes, it's the sagetvservice.exe program. I double-checked after reading about the transcoding issue too.

I think that the unsuported extras were (hopefully) the root cause of my issues.

Matt

[matt91]

I assume this is the fix in the new 6.12 beta:

>Hidden Feature Bug Fix: Added conditionals to the FocusGained hook in the custom malore menus to prevent infinite refreshes.

can anyone confirm that it's fixed?

[blade]

No, it is not. I didn't have the 100% usage issue with the previous beta, but after upgrading this morning I have it and it's already caused a BSOD while recording during primetime and has caused Sage to freeze up twice in less than 30 minutes while trying to watch pre-recorded shows.

I love Sage, but right now the v6 betas are very buggy and unstable. I've never had Sage lockup in almost 2 years until trying v6.

[Opus4]

Originally Posted by matt91

I assume this is the fix in the new 6.12 beta:

>Hidden Feature Bug Fix: Added conditionals to the FocusGained hook in the custom malore menus to prevent infinite refreshes.

can anyone confirm that it's fixed?

_If_ your 100% cpu usage was happening while sitting on the 2-pane malore style menus, then this is the same fix that I posted a link to in my last post, above. If you had 100% cpu usage while on any other menu, then this change has nothing to do with it.

- Andy

[blade]

I guess I should have read the thread more closely. I don't use the malore menus. My server's cpu usage is 0-2% until I launch the client. Then it pegs out at 100% and stays there. I'm using the default stv with the unsupported extras turned off. This happens whether I'm using the service or run the gui.

I also still have the problem where the service hangs up when it is set to automatically start at bootup. I'm going to try and troubleshoot enough to file a bug report, but the problems are so bad I don't know if I can get the box to even function enough to get the data for a bug report.

[Opus4]

The biggest things you would need for a bug report would be the debug logs, for both the server and the client. Debug logging should eb on by default during the beta, so just look for the sagetv_0.txt & sagetvclient_0.txt files in your SageTV dir & save them. If the problem happened on a previous run of the program, look for the _1 versions of those files.

- Andy

[matt91]

Originally Posted by Opus4

_If_ your 100% cpu usage was happening while sitting on the 2-pane malore style menus, then this is the same fix that I posted a link to in my last post, above. If you had 100% cpu usage while on any other menu, then this change has nothing to do with it.

- Andy

I'm pretty sure that this was the problem, as it's now fixed (by me disabling the unsupported extra).

The problem is that when you connect via the MVP, you're somewhat insulated from out-of-control cycles on the server. Even when the CPU was running 90-100%, my videos were running fine. It was only the menus that were *really* unusable. So I wasn't sure exactly when the CPU ramped up.

Again, seems to be fixed now. Thanks...

Matt