PDA

View Full Version : Multiple crashes on clients



ccihon
2016-12-02, 04:20 PM
Since installing the latest version, I have seen quite a number of application errors (crashes with force close) - they most regularly happen after a recording completes and NPVR returns to the GUI, but have also seen them as it sits idling at the recordings, listings, or home display, as it often does. This occurs on two different clients, so while I thought it might be a display or driver issue, I can't imagine it taking place on both units as they are quite a bit different hardware-wise. Did not see these errors on previous versions, and I can accept "close" and relaunch easily without issue - until the next time. - ideas?

Here is what appear in the Event viewer - these particular two errors took place after I stopped viewing last night:

(Event ID 1000 Application Error)

Faulting application name: NextPVR.exe, version: 1.0.0.0, time stamp: 0x58332bd3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0e3884db
Faulting process id: 0x1c74
Faulting application start time: 0x01d24c3c53d7c332
Faulting application path: C:\Program Files (x86)\NPVR\NextPVR.exe
Faulting module path: unknown
Report Id: 7436e4ee-be61-43f2-8baa-efb1b07b58bf
Faulting package full name:
Faulting package-relative application ID:


(Event ID 1026 .net runtime)

Application: NextPVR.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at SlimDX.DataStream.WriteRange(IntPtr, Int64)
at NextPVR.Utility.Direct3DHelper+ElementInternals.Up date(SlimDX.Direct3D9.Device)
at NextPVR.Utility.Direct3DHelper.RenderScreen(System .Collections.Generic.List`1<NUtility.UiElement>)
at NextPVR.ControllerForm.Render(Boolean)
at NextPVR.Program.Main(System.String[])

sub
2016-12-02, 04:31 PM
Are you using the TVListings plugin? We've seen a crash like the one above from it in the past. I think it relates to something it's trying to do with animations. If you are running TVListings, you could try running NextPVR with the "-no3d" command line to see if the problem goes away.

ccihon
2016-12-02, 04:50 PM
Are you using the TVListings plugin? We've seen a crash like the one above from it in the past. I think it relates to something it's trying to do with animations. If you are running TVListings, you could try running NextPVR with the "-no3d" command line to see if the problem goes away.

yep, you guessed it. It is the latest version that was set to function with the standard exe recently updated by the author, though I think the error occurred with the separate patch you had provided to npvr.exe previously. I'll try the "-no3d" switch - what do I lose? maybe I need to move this to the TV Listings forum

sub
2016-12-02, 05:00 PM
yep, you guessed it. It is the latest version that was set to function with the standard exe recently updated by the author, though I think the error occurred with the separate patch you had provided to npvr.exe previously.Yeah, I remember another TVListings user saying they'd had the problem a while, so I don't think it related to the most recent release.


I'll try the "-no3d" switch - what do I lose? Animations are turned off.


maybe I need to move this to the TV Listings forumI'll move it for you.

sub
2016-12-02, 05:03 PM
I'm not a TVListings users, but I do have it installed (for investigating that recent issue). If you know of a set of steps to reproduce the problem, I'll see if I can track down the cause.

ccihon
2016-12-02, 05:27 PM
Knowing it happens now relative to TV Listings and the two modules, TV Recordings and TV Listings, I think you can recreate the error buy allowing a recording to complete from the "TV Recordings" screen, and may see intermittent crash as the video player exits to those screens....doesn't happen every time but often enough you can likely see it. I tend to either launch a live show from "TV Listings" custom guide screen, or from "TV Recordings" view. I'd dump the whole thing if I could train the family an the new (and improved) standard screens, and separately, take the time to clean up all the channel mess I have with both ATSC and Cablecard tuners - lotsa duplication I have always avoided by creating custom TV Listings screens

ccihon
2016-12-08, 04:03 PM
Knowing it happens now relative to TV Listings and the two modules, TV Recordings and TV Listings, I think you can recreate the error buy allowing a recording to complete from the "TV Recordings" screen, and may see intermittent crash as the video player exits to those screens....doesn't happen every time but often enough you can likely see it. I tend to either launch a live show from "TV Listings" custom guide screen, or from "TV Recordings" view. I'd dump the whole thing if I could train the family an the new (and improved) standard screens, and separately, take the time to clean up all the channel mess I have with both ATSC and Cablecard tuners - lotsa duplication I have always avoided by creating custom TV Listings screens


Sub -did you get a chance to test? Posting in hopes maybe Alibert can look into issue, which did not occur with previous versions for me. Adding the "-no3d" flag solved the crashing issue, but removes the animations, and more importantly, makes the screen updates in the UI quite sluggish in response to remote commands.

sub
2016-12-08, 04:22 PM
I had a go at reproducing it, but couldn't get the problem to happen.

ccihon
2016-12-08, 05:52 PM
I had a go at reproducing it, but couldn't get the problem to happen.

Thanks for checking - doing a bit of testing...I turned animations back on, removed the flag, but unchecked "wait for vsync" - early on, no crash yet, and screen far more responsive. What is the potential benefit of the vsync option in "general"? I just got a 4K set and am running at the native 2160 res 60hz, so I think turning the 3d off was an even larger impact than might otherwise be.

gEd
2016-12-08, 11:22 PM
Sub, i am using -no3d and zero crashes. Previously, it would barf quite often after simply watching a recording and then escaping back to the main menu.

alibert
2016-12-09, 07:08 AM
I also tried to reproduce this here without success. It generally sounds like some concurrent modifications to internal structures during screen rendering, which is done much more often if animations are enabled. I may try and add some explicit synchronization when getrenderlist is invoked, however, not sure if this is sufficient.

-alibert

alibert
2016-12-20, 07:07 PM
Hi,

those having random crashes when animations are enabled - could you try the attached version and check if it gets better?

-alibert

ccihon
2016-12-21, 02:23 PM
Hi,

those having random crashes when animations are enabled - could you try the attached version and check if it gets better?

-alibert

thanks for addressing - will try and report back!

ccihon
2016-12-27, 03:55 PM
thanks for addressing - will try and report back!

So having run this TV Listings DLL version on three different machines, I can sy that the number of crashes are reduced, but not entirely eliminated. Hope that helps.

ccihon
2017-01-10, 02:14 PM
So having run this TV Listings DLL version on three different machines, I can sy that the number of crashes are reduced, but not entirely eliminated. Hope that helps.

Hoping there is a solution for this? I am certain the same error is occurring with the new dll version

gEd
2017-01-11, 02:18 AM
Yep I've still been experincing the same crash (and I have animations disabled FWIW). I am using the -no3d option when launching npvr in order to try and prevent further crashes.

ccihon
2017-01-11, 01:55 PM
agree - "-no3d" option prevents the crashes, but in my case on a 4k tv, makes menu and guide navigation very sluggish. I should probably just ditch the TVListings plugin and get used to the standard Guide, which is now improved. Main thing preventing it is that I would need to emulate the listing groups for atsc and cablecard channels I have, eliminating many I don't watch or don't have access to to get a clean guide. I have researched Dirct3D errors with some other apps and am testing a possible work-around. I'm thinking Alibert is focused on other things.

alibert
2017-01-15, 06:51 AM
Sorry that I don't have a solution - I still don't know exactly what is causing the crashes with npvr 3.9.2 so that I could add a workaround here.

Maybe it helps to set EnableAnimations to false (http://www.nextpvr.com/nwiki/pmwiki.php?n=Configuration.Advanced#toc16)?

-alibert

sub
2017-01-15, 07:02 AM
Sorry that I don't have a solution - I still don't know exactly what is causing the crashes with npvr 3.9.2 so that I could add a workaround here.I don't think it's specifially related to 3.9.2, because I've seen a couple of users report this same message when using TVListings in other recent versions of NextPVR.

I tried to reproduce it here but couldn't. From the message, it looks like it might be related something about the way UiElements is being disposed of, or not disposed of (maybe running out of GPU text memory).

ccihon
2017-01-16, 02:37 PM
all the help appreciated - I actually did not see the issue until the latest version, and have used the plugin for a few years. I think I will need to use the standard Guide and Recordings until remedied - thanks!