NPVR 2.2.6 Recording Service Crash

[buribu]

Use that most recent version of unmanaged.dll, and set <CollectEIT> to false, then reproduce the problem and post the logs and I'll take another look.

Hello sub,

so for testing, I set <CollectEIT> to false again, and to get EPG-Information for my important channels I configured XMLTV (didn't thought that this is so easy).

Now my results of testing:

First I made an EPG-Delete and then an EPG-Update in the Settings-Channels-Menu. This ended in a crash of NextPVR at

Code:

Name der fehlerhaften Anwendung: NextPVR.exe, Version: 1.0.0.0, Zeitstempel: 0x4e9081d5
Name des fehlerhaften Moduls: mscorwks.dll, Version: 2.0.50727.5446, Zeitstempel: 0x4d8cdc73

including a crash.mdmp. this event-Informations are looking similar to the crashes of nrecord.exe, I think. (logs at 20111014-npvr.zip)


Second, the normal EPG-Update at 2:00 ended with the "Async stop taking way too long"-message, but the nrecord.exe didn't crash at this point. This time it crashed in the morning before starting a recording. (logs at 20111014-nrecord.zip)

Probably, this info will help a bit more.

[jcjefferies]

Last weekend I had the crash happen some time after "Async stop taking way too long" in my case 2 1/2 hours later after two wakeups. I have been trying to generate "Crash Dumps" without changing the default EIT settings as I can usualy force one after several EPG updates. One produced a c:\temp\crash.mdmp of 280k and the another two I forced a crash dump using Task Manager which produced files of 170MB and 200MB. However after "Async stop taking way too long" the odd thing is that NPVR.exe stops responding and not NRecord.exe which crashes in the Windows logs!!

[buribu]

. However after "Async stop taking way too long" the odd thing is that NPVR.exe stops responding and not NRecord.exe which crashes in the Windows logs!!

Jcjefferies, the nrecord.exe crashes, if the "Async stop taking way too long"-message occurs during the automated epg-update at night. If you use nextpvr to do a manual epg-update and this results in a crash then this happens in npvr.exe.

Can you zip your dumpfiles including the related logfiles and post it here, please? Probably this can help sub to find the error.

[jcjefferies]

When NRecord crashes it most often happens at 02:06 at the end of the scanning phase of the EPG update. Knowing that the error happens sometimes during a Manual Update I tried to force a crash but NPVR.exe crashed not NRecord.exe so didnt think that the crash dumps were of use. I have NRecord set to restart when it crashes so crash dumps in normal use wont be much help by the time I realise there has been a crash.

SUB - Given that I can generate a crash by doing several EPG updates and as NPVR.exe stops responding and NRecord seems ok, what data would be useful to help identify the problem.

[Deev8]

... the nrecord.exe crashes, if the "Async stop taking way too long"-message occurs during the automated epg-update at night.

The recording service crashes following "Async stop taking way too long" under other circumstances as well - I reported one set of circumstances in the original post in this thread.

[BrainStormer]

Got a Crash Again. Same 2 shows a week later. Seems House Starts recording at 9 and then Mike & Molly at 9:30.
Also had a dot net error. (Logs Attached)

[buribu]

Hello sub,

because of the nearly 1300 Views on this thread (and that's not just me who looks every minute for a new answer ), I think this is an important topic for many users of NextPVR.

I just want to ask, if you had a bit of time to have a look at my logs and the crash.mdmp that I posted at 2011-10-14 (Post #31)?

For info: For me the <CollectEIT>-Setting doesn't improve the situation, I still have nrecord.exe-crashes every day/night.

[sub]

I'd agree its an important topic. Its the very top problem on my priority list to solve. Not being able to reproduce the problem does present some challenges for fixing it though. The information I've collected from other users have unfortunately not identified any cause.

So, at this stage the cause is unknown and I haven't been able to work on a fix, but I have been working on a workaround for the next release, which will hopefully avoid the issue.

[buribu]

Hello sub,

in the last days I have made a few more tests. Here my new results:

I do know now, how I can run the NextPVR-System without crashing or "Async stop taking way too long"-messages:

In my case, if the EPG-Source of some channels is set to "DVB/ATSC EPG" - regardless of the setting of the <CollectEIT>-switch - the nrecord.exe-process was crashing. Now I have changed the EPG-Source of all channels to none or XMLTV and since then no more crashes anymore.

[Deev8]

Just to add to the record for this problem - I also installed the patch and set CollectEIT to false in config.xml two weeks ago.

During that time the recording service hasn't crashed, and it had previously been crashing around once per week. Two weeks is probably long enough to suggest that it has improved the situation for me - thanks sub.