NRecord.exe High CPU Utilization

[DParsons]

I've had my PC nearly stop running several times now and I have noticed on the last couple of events that the nrecord.exe has been utilizing all of the CPU while monitoring it with the task manager. This has been happening from v3.8.3 and has just happened for the first time on v3.9.2. Logs attached.

[mvallevand]

Are you sure it is NRecord and NextPVR? I see you coming in from Emby and because of transcoding especially with your h264 source it can be a CPU hog.

Martin

[DParsons]

That is what it said on task manager NRecord.exe. I was trying to take a screenshot but my pc would not work then. It is definitely while watching live tv remotely with emby that seems to trigger this, I've noticed. But because it is nrecord which is NextPRV (I believe) is why I was posting this here. Do you think this is an Emby issue?

[sub]

I can't see anything in the logs which could account for high CPU usage, and I can't remember any reports of this in the past.

If you do a recording in NextPVR, what does the CPU look like? If you do live tv in NexPVR, what does the CPU look like? If you do live tv in Emby, what does the CPU usage look like?

[DParsons]

Emby livetv 20-25%cpu, NextPVR recorded tv 1%cpu, NextPVR live tv 5% CPU. I'll post today's Emby logs, on the Emby forums, after it's starts working normally again so that the whole daily cycle is on the logs. It has started already as it will not work in the mornings even from my home network, it's not just remote access that gives the problems.

[DParsons]

Hello Sub,

I posted my Emby logs on their forum but my response was what is nrecored.exe. So I'll post the screenshot of the CPU event here as well.

[sub]

I've not seen any other reports of 100% CPU from nrecord.exe.

Were those log above captured when it was at 100%, or some time later?

[DParsons]

They are from immediately after it happened.

[sub]

How long does it happen for? I'd like to see the logs from when it's actually happening.

[sub]

I'm not convinced those logs show the problem.

The most recent nrecord.log in there only shows the recording service starting, and only covers a 6 second period of it starting up. No other action is shown.

The previous nrecord.log.1 was from 7 hours earlier.