KazPinkerton 0 Posted April 12, 2018 Share Posted April 12, 2018 So, the app pretty frequently (but not totally consistently, sometimes I can over a day with no problems, sometimes I have days like today where this has happened literally 22 times) hard crashes to the Apple TV menu while I'm watching Live TV. I say it's a 'hard' crash because when I relaunch the app it goes back through the whole 'Starting Up...' bit, which would imply that it was stopped completely. Whenever this happens I reliably get the same exception and stack trace in the server log, and the log messages leading up to the crash take on one of two forms. I see it fail in this way: 2018-04-11 16:05:30.360 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/videos/68c89418cec53a64a07b8dbe247774c5/hls/1b035f8fe46cbd3341c0f6f9d871d069/1b035f8fe46cbd3341c0f6f9d871d0692.ts. Host=192.168.1.2:8096, X-Playback-Session-Id=F23116B0-7CF9-4759-906C-52ADA1EB70E9, Accept=*/*, User-Agent=AppleCoreMedia/1.0.0.15K600 (Apple TV; U; CPU OS 11_2_6 like Mac OS X; en_us), Accept-Language=en-us, Accept-Encoding=identity, Connection=keep-alive 2018-04-11 16:05:30.362 Info HttpResultFactory: Transmit file C:\Users\Public\Videos\Pause Buffer\transcoding-temp\1b035f8fe46cbd3341c0f6f9d871d0692.ts 2018-04-11 16:05:30.365 Info HttpServer: HTTP Response 200 to 192.168.1.167. Time: 4ms. http://192.168.1.2:8096/emby/videos/68c89418cec53a64a07b8dbe247774c5/hls/1b035f8fe46cbd3341c0f6f9d871d069/1b035f8fe46cbd3341c0f6f9d871d0692.ts 2018-04-11 16:05:30.495 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/videos/68c89418cec53a64a07b8dbe247774c5/hls/1b035f8fe46cbd3341c0f6f9d871d069/1b035f8fe46cbd3341c0f6f9d871d0693.ts. Host=192.168.1.2:8096, X-Playback-Session-Id=F23116B0-7CF9-4759-906C-52ADA1EB70E9, Accept=*/*, User-Agent=AppleCoreMedia/1.0.0.15K600 (Apple TV; U; CPU OS 11_2_6 like Mac OS X; en_us), Accept-Language=en-us, Accept-Encoding=identity, Connection=keep-alive 2018-04-11 16:05:30.497 Info HttpResultFactory: Transmit file C:\Users\Public\Videos\Pause Buffer\transcoding-temp\1b035f8fe46cbd3341c0f6f9d871d0693.ts 2018-04-11 16:05:30.501 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/8ad01bc707e9447c8ccf6d66c0bbc13b/stream.ts. UserAgent: Lavf/58.3.100 2018-04-11 16:05:30.536 Info HttpServer: HTTP POST http://192.168.1.2:8096/emby/Sessions/Playing. UserAgent: Emby/3 CFNetwork/893.14 Darwin/17.4.0 2018-04-11 16:05:30.541 Info HttpServer: HTTP Response 200 to 192.168.1.167. Time: 46ms. http://192.168.1.2:8096/emby/videos/68c89418cec53a64a07b8dbe247774c5/hls/1b035f8fe46cbd3341c0f6f9d871d069/1b035f8fe46cbd3341c0f6f9d871d0693.ts 2018-04-11 16:05:30.543 Info HttpServer: HTTP Response 204 to 192.168.1.167. Time: 7ms. http://192.168.1.2:8096/emby/Sessions/Playing 2018-04-11 16:05:32.607 Info HttpServer: HTTP POST http://192.168.1.2:8096/emby/Sessions/Playing/Progress. UserAgent: Emby/3 CFNetwork/893.14 Darwin/17.4.0 2018-04-11 16:05:32.608 Info HttpServer: HTTP Response 204 to 192.168.1.167. Time: 1ms. http://192.168.1.2:8096/emby/Sessions/Playing/Progress 2018-04-11 16:05:33.692 Info HttpServer: HTTP Response 200 to 192.168.1.167. Time: 3351ms (slow). http://192.168.1.2:8096/emby/LiveStreams/MediaInfo 2018-04-11 16:05:33.750 Error HttpServer: Error in HttpListenerResponseWrapper: An existing connection was forcibly closed by the remote host *** Error Report *** Version: 3.3.0.0 Command line: C:\Users\User\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: C:\Users\User\AppData\Roaming\Emby-Server\programdata Application directory: C:\Users\User\AppData\Roaming\Emby-Server\system System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) System.Net.Sockets.SocketException at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) 2018-04-11 16:05:33.750 Info HttpServer: HTTP Response 500 to 127.0.0.1. Time: 3250ms (slow). http://127.0.0.1:8096/LiveTv/LiveStreamFiles/8ad01bc707e9447c8ccf6d66c0bbc13b/stream.ts and this way Playback-Session-Id=F23116B0-7CF9-4759-906C-52ADA1EB70E9, Accept=*/*, User-Agent=AppleCoreMedia/1.0.0.15K600 (Apple TV; U; CPU OS 11_2_6 like Mac OS X; en_us), Accept-Language=en-us, Accept-Encoding=gzip, Connection=keep-alive 2018-04-11 17:06:01.793 Info HttpServer: HTTP Response 200 to 192.168.1.167. Time: 3ms. http://192.168.1.2:8096/emby/videos/68c89418cec53a64a07b8dbe247774c5/live.m3u8?DeviceId=A11111E3-21A9-4F4B-8686-73F2AE099653&MediaSourceId=0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d&VideoCodec=h264&AudioCodec=aac,ac3,mp3&AudioStreamIndex=-1&VideoBitrate=39872000&AudioBitrate=128000&MaxWidth=1920&PlaySessionId=58a8fbb4dd154141b8cc3a5fd748a490&LiveStreamId=a17c75760a04e99b68cf766e11316e1c_09efa0d56b934a82adec00a87b837fb0_0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d&EnableSubtitlesInManifest=true&RequireAvc=false&SegmentContainer=ts&BreakOnNonKeyFrames=True&h264-profile=high,main,baseline,constrainedbaseline&h264-deinterlace=true&h264-level=42&audiochannels=6&TranscodeReasons=ContainerNotSupported,VideoCodecNotSupported,AudioCodecNotSupported 2018-04-11 17:06:02.599 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source. 2018-04-11 17:07:01.805 Info App: Transcoding kill timer stopped for JobId cc07f64a417543f4b55f71f08ee557be PlaySessionId 58a8fbb4dd154141b8cc3a5fd748a490. Killing transcoding 2018-04-11 17:07:01.805 Info App: Stopping ffmpeg process with q command for C:\Users\Public\Videos\Pause Buffer\transcoding-temp\1b035f8fe46cbd3341c0f6f9d871d069.m3u8 2018-04-11 17:07:01.978 Info App: FFMpeg exited with code 0 2018-04-11 17:07:01.978 Info App: Deleting partial stream file(s) C:\Users\Public\Videos\Pause Buffer\transcoding-temp\1b035f8fe46cbd3341c0f6f9d871d069.m3u8 2018-04-11 17:07:01.978 Info MediaSourceManager: Closing live stream 09efa0d56b934a82adec00a87b837fb0_0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d with provider LiveTvMediaSourceProvider 2018-04-11 17:07:01.978 Info App: Closing live stream from Emby, stream Id: 0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d 2018-04-11 17:07:01.978 Info App: Live stream 0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d consumer count is now 0 2018-04-11 17:07:01.978 Info App: Closing live stream 0c5adb36b91244e78a77a3a11e25dc97_native_3d0b7e7e419c5a8ecde09a3f72d6f76e_6c9c774ec5bcd6d95d472bf42ae96d2d 2018-04-11 17:07:01.978 Info App: Closing SharedFileStream 2018-04-11 17:07:01.984 Error HttpServer: Error in HttpListenerResponseWrapper: An existing connection was forcibly closed by the remote host *** Error Report *** Version: 3.3.0.0 Command line: C:\Users\User\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: C:\Users\User\AppData\Roaming\Emby-Server\programdata Application directory: C:\Users\User\AppData\Roaming\Emby-Server\system System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) System.Net.Sockets.SocketException at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) 2018-04-11 17:07:01.984 Info HttpServer: HTTP Response 500 to 127.0.0.1. Time: 3704942ms. http://127.0.0.1:8096/LiveTv/LiveStreamFiles/8ad01bc707e9447c8ccf6d66c0bbc13b/stream.ts 2018-04-11 17:07:02.286 Info App: Deleting temp files C:\Users\Public\Videos\Pause Buffer\livetv-2908.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-2.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-3.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-4.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-5.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-6.ts, C:\Users\Public\Videos\Pause Buffer\livetv-2908-7.ts The first scenario is, by far, the most common. Both scenarios result in the Apple TV app crashing. I can provide whatever other details you might need, just ask. Link to comment Share on other sites More sharing options...
Luke 37008 Posted April 12, 2018 Share Posted April 12, 2018 hi @@KazPinkerton, can you try updating to the latest version of emby server? thanks ! Link to comment Share on other sites More sharing options...
KazPinkerton 0 Posted April 12, 2018 Author Share Posted April 12, 2018 I'll give it a shot and let you know how it goes. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now