Jump to content


Photo

Computer and EmbyServer freeze when playing a video while it is recording

MacOS Docker

  • Please log in to reply
6 replies to this topic

#1 adamcureton OFFLINE  

adamcureton

    Member

  • Members
  • 11 posts
  • Local time: 12:32 PM

Posted 19 December 2019 - 07:11 PM

After I start recording from an M3U source, wait a bit, and then go to Recordings and play the video, it plays fine for about 20 minutes and then Emby Server and my computer become largely unresponsive.  My computer, in particular, loses all network connections; many applications will not run or exhibit strange behavior; it won't even shut down properly, so I have to turn off the power. 

 

Note that this procedure produces the same problem every time, regardless of how long I let the video record before playing and whether throttling is enabled or not.

 

Playing videos for which recording has completed works fine.

 

Logs are attached.

 

Also, I noticed that my system log reports the following error around the time the crash occurs:

kernel    void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): IntelAccelerator prodding blockFenceInterrupt

I thought this issue might be macOS specific (I'm on Catalina 10.15.2), so I installed the Emby Server Docker container, but I get the same behavior - my computer doesn't freeze, but the container becomes unresponsive, forcing me to restart it.

Attached Files



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152600 posts
  • Local time: 01:32 PM

Posted 19 December 2019 - 07:52 PM

Hi there, does this only happen if you watch and record at the same time? Is the system running out of free space when it happens due to the live tv temp files?



#3 adamcureton OFFLINE  

adamcureton

    Member

  • Members
  • 11 posts
  • Local time: 12:32 PM

Posted 19 December 2019 - 08:30 PM

Hi @Luke.  Yes, this only happens when I watch and record at the same time.  HDD space is not the cause because I have 100+GB of free space on the volume with the transcoding-temp folder.  I've also monitored the folder while simultaneously watching and recording and the total size is not nearly that large.  And I've tried the transcoding-temp folder on other, much larger, volumes.



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152600 posts
  • Local time: 01:32 PM

Posted 20 December 2019 - 01:06 AM

How fast is the drive? Is it possible it just can't handle all of the simultaneous I/O ?



#5 adamcureton OFFLINE  

adamcureton

    Member

  • Members
  • 11 posts
  • Local time: 12:32 PM

Posted 20 December 2019 - 08:55 AM

The drive is an NVME SSD.  I've also tried moving the folder to a slower SATA SSD, with the same results.  And, my Emby Server can record at least four simultaneous streams while I also watch previously completed recordings.  The problem only happens when I try to watch one while it is recording. 

 

I suppose there could be some hardware or driver issue (e.g. NIC, as I also get some weird network buffer errors in my system log or Intel GPU, which is apparently referenced in the error I included in my original post), but it's strange that the Docker container exhibits the same behavior, at least on my system.

 

Anyway, thanks for your help!  Perhaps nothing can be done, but I thought I'd mention this problem in case it arises for others. 



#6 adamcureton OFFLINE  

adamcureton

    Member

  • Members
  • 11 posts
  • Local time: 12:32 PM

Posted 20 December 2019 - 06:28 PM

Hi @Luke.  I have an update that may or may not be helpful.  I started a recording in Emby Server, gave it a few minutes, and then manually ran this command (taken from the Emby log file) from a shell, referencing the correct id of the recording I started:

/Applications/EmbyServer.app/Contents/MacOS/ffmpeg -loglevel +verbose -analyzeduration 3000000 -fflags +discardcorruptts+fillwallclockdts  -f mpegts -i "http://127.0.0.1:8096/LiveTv/LiveRecordings/7704cdd29b3e43a1982bf43122e57c96/stream" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -sn -c:v:0 copy -vsync -1 -codec:a:0 copy -metadata:s:a:0 language=eng -disposition:a:0 default -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3  -individual_header_trailer 0 -segment_format mpegts -segment_write_temp 1 -segment_list_entry_prefix "hls/1e93ebec08c8eea895fc7d70dc8dc7a1/" -segment_list_type m3u8 -segment_start_number 0 -segment_list "/Volumes/VM/temp/transcoding/transcoding-temp/1e93ebec08c8eea895fc7d70dc8dc7a1.m3u8" -y "/Volumes/VM/temp/transcoding/transcoding-temp/1e93ebec08c8eea895fc7d70dc8dc7a1%d.ts"

It's been going without incident for over an hour (whereas when I attempt to record and watch the same video in Emby, everything craps out after about 20 minutes).  This suggests, I guess, that the problem I'm having is not hardware or system specific, but may have something to do with some part of Emby Server.



#7 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152600 posts
  • Local time: 01:32 PM

Posted 23 December 2019 - 01:01 PM

Thanks for the info. We'll take a look.





Also tagged with one or more of these keywords: MacOS, Docker

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users