Jump to content

App crashes 4-5 seconds into video playback.


therawuncut

Recommended Posts

therawuncut

Seems to happen with every single file played via LAN, and has for a few months.

 

Device - Kindle Fire HDX

OS - Fire OS 5.6.1.0

 

Log file is attached.

server-63659497285.txt

Edited by therawuncut
Link to comment
Share on other sites

therawuncut

I uninstalled and reinstalled from the Play store, so it *should* be the most recent.

 

Oddly enough, the Devices section in the app shows a garbled 2.9.92 (which I know isn't the most recent).

 

When I relaunch the app, the most recently played video will populate back into my notifications pulldown, but clicking it does nothing at all.  Is this possibly a device issue?

 

 

nVQBv2Q.png

Edited by therawuncut
Link to comment
Share on other sites

maxxoverclocker

I don't want to thread hijack but I have the same issue. Emby app for Android (latest) crashes 5 seconds in on nearly every video in the library. Server logs show an HTTP 500 error immediately followed by a "Error in SharpWebSocket" error. iOS, HTML5, and Windows 10 apps work just fine. Let me know if I should create my own thread but this appears to be the exact same issue for me.

 

This happens when direct playing, streaming, https, http... I've tried everything I can think of.
 

2018-04-19 22:45:13.589 Info HttpServer: HTTP Response 500 to xxx.xxx.xxx.xxx. Time: 8852ms (slow). https://emby.local:8920/Videos/b57388f0a7e6b62755b24bda883203dd/stream.mkv?Static=true&mediaSourceId=b57388f0a7e6b62755b24bda883203dd&deviceId=47736fe9686a2a38&Tag=ae12a2a7327d114a44fafc233a0e65bb
2018-04-19 22:45:13.589 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.

 

Link to comment
Share on other sites

gaaten

 

I don't want to thread hijack but I have the same issue. Emby app for Android (latest) crashes 5 seconds in on nearly every video in the library. Server logs show an HTTP 500 error immediately followed by a "Error in SharpWebSocket" error. iOS, HTML5, and Windows 10 apps work just fine. Let me know if I should create my own thread but this appears to be the exact same issue for me.

 

This happens when direct playing, streaming, https, http... I've tried everything I can think of.

 

2018-04-19 22:45:13.589 Info HttpServer: HTTP Response 500 to xxx.xxx.xxx.xxx. Time: 8852ms (slow). https://emby.local:8920/Videos/b57388f0a7e6b62755b24bda883203dd/stream.mkv?Static=true&mediaSourceId=b57388f0a7e6b62755b24bda883203dd&deviceId=47736fe9686a2a38&Tag=ae12a2a7327d114a44fafc233a0e65bb
2018-04-19 22:45:13.589 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.

 

 

Same issue here as well got the same exact log entries.  Runnig a Kindle fire HD 8 2017 model playback stops after 4-5 seconds (max 10) Direct play or transcoding makes no difference the app will crash and then "continue" playing in the status bar. The app does not seem to be recognized as dead by android os so killing the app in the task switcher is the only way to get rid of the notification, as the app is not possible to switch back in to. 

 

My wifes Galaxy S7 experience the same issue, she mostly downloads files for offline viewing and they also makes the app crash. Only device currently capable of using video is my Nexus 6P running Oreo 8.1 

 

On the Amazon tablet I also tried switching the media playback engine to awesomeplayer instead of nuPlayer, but no effect, had to settle for VLC as an external player which is far far from ideal. 

 

All devices has been tested with beta version and stable. 

Edited by gaaten
Link to comment
Share on other sites

  • 2 weeks later...
echoxxzz

I have very similar issue. The last stable version that works on my Samsung S2 tablet is 2.9.76. For now I've disabled auto updates in the Playstore and will remain on 2.9.76. For those looking for this older release I found it on apkpure.com.

Link to comment
Share on other sites

echoxxzz

Just tested on my Samsung S8 phone and exact same problem. Once I start playing a video the device becomes totally unresponsive and and I have to hit the power button a few times to get a screen back whereby I can than go into android setting, apps, and force emby to close.

 

This happens on all versions of Emby since 2.9.76. I'm charging up my old galaxy t320 tab running LineageOS to see if this is a Samsung problem.

Link to comment
Share on other sites

echoxxzz

I took gaaten's suggestion to try an external player and using MX Player Pro it's now super responsive. If I slide ahead in the video it instantly starts at the new time slot.

Link to comment
Share on other sites

maxxoverclocker

Please try this again with the next release of the app, thanks.

 

Hi Luke, by next release, do you mean next release after 2.9.92? or is 2.9.92 the release you are referring to? I just tested after upgrading to the latest version of Emby server and it appears to still be an issue. (After clearing the android cache, removing all data, uninstalling, fresh install, etc...)

Link to comment
Share on other sites

maxxoverclocker

I mean the one that will come after that. Thanks.

 

Great, thanks! I'll be on the lookout for it.

Link to comment
Share on other sites

aahmyu

Any updates on this? Phone becomes slow and can't interact with the app interface. Screen goes to sleep while playing videos.

Link to comment
Share on other sites

  • 2 weeks later...
tekfranz

A similar issue is happening on my Asus Zen Pad.

Our IOS and Windows Browser Devices work fine.

But the stream drops and the App goes black at about 5 minutes of playing.

We have tried a direct local connection and EMBY Connect and both behave the same.

 

I did find a Work-Around and that is to use the Chrome Browser and also use Add to Desktop to make a Shortcut to EMBY.

Edited by tekfranz
Link to comment
Share on other sites

Ok thanks for the info. We'll hopefully have a new beta up soon. Thanks.

Link to comment
Share on other sites

tekfranz

Also, we have had some success white-listing our Emby URL and IP in our content filtering software...though it was not being flagged as blocked.

Link to comment
Share on other sites

  • 1 month later...
maxxoverclocker

Ok thanks for the info. We'll hopefully have a new beta up soon. Thanks.

 

Hey Luke,

 

No change with the new version that was just released :(

Link to comment
Share on other sites

maxxoverclocker

Hmmm. Can you provide a sample video for testing?

 

Certainly! The following crashes between 21 and 48 seconds into the title. Let me know if you need the actual media file. 

 

Media Info
Video
Title720P H264
CodecH264
AVCYes
ProfileHigh
Level41
Resolution1280x720
Aspect ratio16:9
AnamorphicNo
InterlacedNo
Framerate23.9760227
Bitrate3817 kbps
Bit depth8 bit
Pixel formatyuv420p
Ref frames1
NAL4
Audio
TitleEng AAC stereo Default
Languageeng
CodecAAC
ProfileLC
Layoutstereo
Channels2 ch
Bitrate192 kbps
Sample rate44100 Hz
DefaultYes
Subtitle
TitleEng
Languageeng
CodecSRT
DefaultNo
ForcedNo
ExternalYes
Containermkv
Path\\nas\Media\Movies\Toy Story Toons Partysaurus Rex (2012)\Toy Story Toons Partysaurus Rex (2012).mkv
 
The following log entries are generated on the server at the immediate time of the crash:
 
2018-07-13 12:42:59.567 Info HttpServer: HTTP Response 500 to 10.40.1.142. Time: 52326ms (slow). http://10.10.1.74:8096/emby/Videos/c4b64fc3f07dfc62a1f7c6f8a106cec8/stream.mkv?Static=true&mediaSourceId=c4b64fc3f07dfc62a1f7c6f8a106cec8&deviceId=47736fe9686a2a38&Tag=bfb2c8e761a17267eb54cd1ca409cbb0 
2018-07-13 12:42:59.567 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.
Interestingly enough, I manually connect all of my devices to port 8920 (https), I'm not sure why 8096 (http) shows up in the logs.
Link to comment
Share on other sites

gaaten

Hi as the previous commenters have indicated still no change with the latest Beta. App closes after a short while playing back any video file in my library. This was not the case with earlier versions prior to my first comment in this thread. This affects 3 different fire hd devices. Oh and emby thinks it is continuing playback in the notification list.only way to remove is to restart the app and then force close.

Edited by gaaten
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...