Since some days I found that Emby Docker is spending a lot of system resources. Their logs are full of this:

Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0178886 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0004245 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001085 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0011258 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0023471 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0002163 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0003186 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 8.1E-05 seconds
Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0056427 seconds
Info App: Starting entry point Emby.LiveTV.EntryPoint
Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json 
Info LibraryMonitor: Watching directory with new FileSystemWatcher for /config/data/livetv/recordings for item 67505
Info LiveTV: Loading live tv data from /config/data/livetv/timers
Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0 - Succeeded
Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0285124 seconds
Info App: Starting entry point Emby.LiveTV.RecordingNotifier
Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0018785 seconds
Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint
Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0026949 seconds
Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0017118 seconds
Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint
Info Notifications: Registering event nofitier Emby Server User Notifications
Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0108064 seconds
Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0015602 seconds
Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 9.19E-05 seconds
Info App: All entry points have started

 

And top file is attached.

 

Any idea?

 

Thank you

 

 

I'm curious if you made any progress on this....

 

For the past month every couple of days my unRAID server becomes unresponsive.  After a lot of troubleshooting, I finally discovered that my emby container would grow in memory usage until it used up all available memory and then crash the entire server.

 

emby is the only docker I set to use host and not bridge.  I changed this so the automatic discovery worked. It had been working fine in this mode for more than a year.

 

I'm wondering with all the macvlan vs. ipvlan stuff if something is up with that network setting.  I changed it to bridge and I'm monitoring to see if memory usage grows. so far it seems to be working better.

 

I do have those same errors in my logs as well.

Try and ask on the Emby forum at https://emby.media/community/index.php

They are usually very fast at answering.