quackpipe 11 Posted January 25, 2021 Posted January 25, 2021 I noticed my computer was acting a little sluggish and when I opened task manager my memory was climbing past 90% and then floated around 98%. Emby Server was running in the background eating up about 6.3GB of ram while one user was watching something through directplay. They watch this particular series frequently and I've never seen the application eat up that much memory. I have 16GB total memory and the only thing I was doing out of the ordinary was exporting a batch of large 1080p videos through adobe media encoder. I restarted the server application through the web portal and once it booted up it floated around 130-150MB of memory, which is where it's at now. Just wondering if anyone has experienced this. I'm running 4.5.4.0 on windows 10
Luke 42078 Posted January 25, 2021 Posted January 25, 2021 Hi there, please attach the emby server log from when this happened. thanks.
quackpipe 11 Posted January 25, 2021 Author Posted January 25, 2021 Attached, Should be closer to the bottom before the restart. Not sure it you wanted me to clear anything our from earlier in the day. embyserver-63747186656.txt
Carlo 4561 Posted January 26, 2021 Posted January 26, 2021 10 hours ago, quackpipe said: I noticed my computer was acting a little sluggish and when I opened task manager my memory was climbing past 90% and then floated around 98%. Emby Server was running in the background eating up about 6.3GB of ram while one user was watching something through directplay. They watch this particular series frequently and I've never seen the application eat up that much memory. I have 16GB total memory and the only thing I was doing out of the ordinary was exporting a batch of large 1080p videos through adobe media encoder. I restarted the server application through the web portal and once it booted up it floated around 130-150MB of memory, which is where it's at now. Just wondering if anyone has experienced this. I'm running 4.5.4.0 on windows 10 Hi, Did you happen to look to see what application or process was using that memory?
quackpipe 11 Posted January 26, 2021 Author Posted January 26, 2021 5 hours ago, cayars said: Hi, Did you happen to look to see what application or process was using that memory? I didn’t click on the specific processes tab but the emby application was taking that 6.3GB of memory.
speechles 2055 Posted January 26, 2021 Posted January 26, 2021 (edited) Was there a forked child process that was also open? For example... did ffmpeg also show as running but using no CPU %? Since ffmpeg is a child of Emby it can also cause the footprint in RAM to become obscene. Next time this happen check to see if there is a rogue ffmpeg and kill it. That should regain your RAM as soon as you do kill that ffmpeg process that is stuck. That might be all this is. You are safe to kill all ffmpeg process even if someone is using one of them. Emby server will notice the sigkill and recreate the ffmpeg children as needed. This means that users won't know you killed their ffmpeg as they are watching because the server will restart that ffmpeg process for them as soon as it needs more chunks. Edited January 26, 2021 by speechles 1
quackpipe 11 Posted January 26, 2021 Author Posted January 26, 2021 1 hour ago, speechles said: Was there a forked child process that was also open? For example... did ffmpeg also show as running but using no CPU %? Since ffmpeg is a child of Emby it can also cause the footprint in RAM to become obscene. Next time this happen check to see if there is a rogue ffmpeg and kill it. That should regain your RAM as soon as you do kill that ffmpeg process that is stuck. That might be all this is. You are safe to kill all ffmpeg process even if someone is using one of them. Emby server will notice the sigkill and recreate the ffmpeg children as needed. This means that users won't know you killed their ffmpeg as they are watching because the server will restart that ffmpeg process for them as soon as it needs more chunks. Great question. I'll watch it. I wish I took a screenshot of the running processes at the time. It had never happened before.
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