One-off unexplained crash

[bgowland]

sub - not sure we'd ever come to the bottom of this but I thought I'd post it FYI...

GB-PVR has been stable for me for a very long time but this evening I put the PC monitor on to find one of those 'Do you want to send to MS..." unhandled exception messages with GBPVRRecordingService as the faulting application.

There were two recordings actually running but stupidly I clicked the 'Dont Send' button which terminated the service - I'd just woken up from a nap so brain wasn't in gear.

Anyway - not sure what the cause was. It appears that something happened around 8:05pm - the App log shows...

Faulting application GBPVRRecordingService.exe, version 1.0.2614.26052, faulting module System.ni.dll, version 2.0.50727.42, fault address 0x00446fdb.

As I said, I'd just woken up so it took me a while to realise the service wasn't running - the systray app refused to open and trying to start the service manually told me that the service had started then stopped. The relevant App log entry for that is...

Service cannot be started. System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at System.Net.Sockets.TcpListener.Start()
at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(Int32 port)
at GBPVR.RecordingService.x116139cea0d00aa9.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

I'm guessing that was just as a result of the Remoting objects not being cleaned up when the service crashed.

I rebooted (around 9:45pm) and things have been fine since. The only thing that has changed on my machine recently was a few MS updates which I'd applied about 12 hours earlier but several recordings have worked fine since then.

The only GBPVR 'event' that ties in with the 8:05pm applog entry is the ending of a recording (normal finish time 8pm + 5 mins post padding). Programme name 'A Pocket Full of Posies' on BBC4 which is a DVB-T channel so the recording would have been dvr-ms with an ASAP transcode to MPEG-2. When I rebooted the machine the transcode started up so it was obviously still in the transcode queue.

I've included all logs but can't see anything relevant myself.

Cheers,
Brian

[sub]

I'm guessing that was just as a result of the Remoting objects not being cleaned up when the service crashed.

Yeah, that'd be my guess. In theory when the process dies, Windows should free up any sockets that were in use, but it may not have for some reason.
If it happens again, you could try running http://www.microsoft.com/technet/sysinte...pView.mspx to see what sockets it thinks are in use.

[bgowland]

OK - I've downloaded TcpView - I'll let you know what I find if it happens again.

Cheers,
Brian