Daily Timed Recording conflicts with self, eats cpu, corrupts db - possible ?

[Gaurav]

Am using Sage 5.0.4

i have recently setup a daily timed recording to record a ppv sporting event.

The timed recording shows up as conflicting with itself on the 8th day.
I had read it was a bogus warning and ignored it.

The bigger problem is sagetvservice.exe has sporadically started consuming 100%CPU. Stopping the service corrupts the database. I have to then restore a previously backed up wiz.bin. It takes about 10 mins to re-start the service.

I am guessing the conflict is causing the cpu usage which is causing the locks which are causing the corruption.

Any thoughts ?

[Gaurav]

Originally Posted by Gaurav

daily timed recording shows up as conflicting with itself. I am guessing the conflict is causing the cpu usage

can someone confirm if this is a known issue in 5.0.4 ?

[attaboy]

I am using V5.0.2.90 and I have a weekly timed recording setup for Saturday and Sunday. After a while it develops a conflict with itself. I have 2 tuners and 2 versions of the recording actually get created. I have not seen any other issues resulting from this, such as the high CPU usage that you mention.

[itsanogo]

I have the same issue.... my timed recordings are conflicting with themself.
As attaboy, I don't have the other issues you are mentionning.

Hopefully it will be fixed in the next release.

[Gaurav]

guess that means somthing else is causing the CPU usage...hmmm...scratching my head...

[nielm]

Have either of you reported this to Sage?

[Gaurav]

Originally Posted by nielm

Have either of you reported this to Sage?

I had read some old posts about timed recordings generating false conflicts and assumed Sage already knew about it and probably fixed it in v6.

The big issue for me, is the 100% CPU plateaus. Apparently it's not linked to the conflict thing and calls for more investigation on my part before i report it.

BTW - i read people are having CPU issues in v6 related to Malore's menus.
Could i be seeing the same thing in v5 ? or is it new to v6 ?

[nielm]

Originally Posted by Gaurav

I had read some old posts about timed recordings generating false conflicts and assumed Sage already knew about it and probably fixed it in v6.

The big issue for me, is the 100% CPU plateaus. Apparently it's not linked to the conflict thing and calls for more investigation on my part before i report it.

BTW - i read people are having CPU issues in v6 related to Malore's menus.
Could i be seeing the same thing in v5 ? or is it new to v6 ?

Please report it -- otherwise it may never get fixed!

Re Malore menus CPU 100% issue -- this was in the SageTV process, not the service, so you may want to contact support for this as well...

(Edit: above is incorrect: see Opus4's message)

[Opus4]

The 100% cpu issue with the 2-pane malore menu could happen in the service if you are using that menu on an MVP, but I don't know whether it was an issue in v5. I don't think so, but I'm not sure.

If using an MVP... The easy test would be to stop using the 2-pane menus & see what happens. Or, see whether the 100% cpu usage continues when no MVP has focus on the right-hand side of those 2 panes.

- Andy

[BobPhoenix]

Originally Posted by Opus4

The 100% cpu issue with the 2-pane malore menu could happen in the service if you are using that menu on an MVP, but I don't know whether it was an issue in v5. I don't think so, but I'm not sure.

Based on my experiences converting the version 5 Malore menus to SageMC it was an issue. BUT (isn't there always one) I was runing the V5 Malore menus on SageTV V6.0.11 and SageMC so that may have been the cause and V5 Malore menus on SageTV V5.0.4 and the Default STV may be fine.

[Gaurav]

I have noticed that the CPU usage peaks when i delete a recording. The MVP freezes (goes black) for 15 to 30 seconds before returning to the menu.
Even after the recording is deleted, the CPU usage stays at 100% for a while.

These days i am making a daily 9 hour timed recording (Cricket Matches).
Deleting one of these recordings sometimes takes upto 10mins and after that the CPU stays at 100% for upto an hour.

I am using Malore's 2 pane menu on an MVP.
Will revert to the Sage menu and see if it helps.
It could even be an indexing/db maintainance issue.

[Gaurav]

Originally Posted by Gaurav

Deleting one of these recordings sometimes takes upto 10mins and after that the CPU stays at 100% for upto an hour.

Whoa..it happened again. I cancelled the timed recording in progress. The CPU went upto 100%, the MVP froze for 15 mins and went back to the menu. The recording is still visible in the menu with a yellow border. There is no longer an option to cancel the recording (guess it's being cleaned up). Meanwhile the CPU usage is at 100% since the past 30 mins. WIZ.BIN has bloated from 10M to 25M.

You guys think i should report this ? I guess i'll need to reproduce this in debug mode.

[Opus4]

Originally Posted by Gaurav

You guys think i should report this ?

It can't hurt & if they don't already know about it, that's the only way to bring it up.

I don't remember whether there were any recent changes for something like this.

- Andy

[Gaurav]

alright, so i lost my wiz.bin yesterday. After it bloated upto 25M, nothing i tried could "thaw" Sage.

I tried upgrading to v6 hoping the db upgrade might fix it but no luck.
Eventually i replaced the db with a backup from the last upgrade (5.0.2).
Now everything's happy and snappy (all my recordings moved to the library but it could have been worse!).
Even recording deletion is fast. I think the slow deletion was a symptom rather than a cause.

Since my trouble started after i created the daily timed recording, i am going to report it to Sage as a possible cause.