Search the Community

Hello everyone, I'm experiencing a problem with Emby Server running on Windows Server where after some time, the memory usage escalates and nearly maxes out all available memory resources. To resolve this, I have to close and reopen Emby, which only temporarily fixes the issue, as it reoccurs within a few days. Has anyone encountered a similar issue or could possibly point out what might be causing this memory leak? Any advice on how to troubleshoot or fix this would be greatly appreciated. Thank you for your assistance!

embyserver (3).txthi guys, emby server taking 95-98% of 32GB ram, i have attached the logs for you to check. thanks

Host OS：openwrt Kernel Version 5.4.108 Docker：20.10.6 (API: 1.41) emby server：docker 4.6.0.38 Feature Request： 1：give an option to use host memory as cache folder and can set an memory size limit,when cache run out , clear the oldest transcode file. 2：give an option to only allow iptv transcode. reason： 1：As most of client device such as iphone、android tv have very powerful cpu and do not need transcode,I only need transcode when watching IPTV. 2：My host os installed in an ssd drive with a data write limit and transcode produce mass data write. 3：My host have very large memory. Thank you very much for your hard work.

Hi all, Emby is killing my Kodi and my clock! I use a rooted Amazon fire TV 4k stick with an Ethernet USB adapter running Kodi 18.7.2 and the latest Emby addon. I also run this translucent clock app. So, I start Kodi, wait for Emby to welcome me, and start playing Das Boot. About 5 minutes into the gunfight the clock will go kaput. Couple of minutes later, video will stutter, then stop, then Kodi will go kaput as well. The clock vanishes at 85% memory usage, and Kodi itself will die at 89%. If I disable the Emby addon, and restart Kodi, then memory usage, as reported by Kodi itself, will hover around 70%. The clock stays put, and not kaput . This is a bummer because, while I can get new data into the DB by syncing on another box and then copying the DB files, I cannot sync watched status. Would a COVID-19 coding hero look into this memory usage and some way to reduce it? As it stands right now I either use EmbyCon, or I enable and disable the addon to get syncs. Could you please make it so its memory footprint is friendlier to small devices? Lastly, what other data can I get you from my system? Any logs? Thank you! F.

Hi, I have my Emby server on Shield TV, and everything works fine unless I want to transcode files bigger than ~2GB. The transcoding process causes the Shield to run out of memory (RAM) and it restarts the Emby Server. No error is displayed on logs since the restart is caused by the lack of memory (I checked that trough adb access to my Shield). This problem occurs during conversion (sync) or transcoding during playback. I have already tried the following Emby versions: 4.1.1.0 4.2.0.18 4.2.0.19 4.2.0.20 You can check the transcoding log in attachment. Tips for developers: I don't know, but the -rtbufsize keyword for ffmpeg could limit the amount of RAM used in the process. Could this trick be an easy way to overcome this issue? Thank you very much. ffmpeg-transcode-.txt

I searched the forum and did not find anything similar for ET. I would very much like to see the EPG remember the last channel tuned. Like the Emby ATV version. Tune to a channel watch for a period, stop and end up back at the same channel in the guide. What I am currently seeing (using beta here) is igoes back to the first channel in th guide. I know it appears ET uses the same EPG as the web app where I am also seeing the same behavior. Don't know if it is possible or not, sure would be nice to have! Thanks for reading and considering!

I am a new Emby user ... I have been using Next PVR with Kodi for almost a year now, but I was looking for something a bit more reliable and "wife" approved. My particular interest is for PVR use, and I have 3 Silicon Dust HDHomerun tuners I use. I have a Prime that is connected to Comcast, and for OTA I have the Connect and the Extend, a total of 4 OTA and 3 Cable tuners. I tested Plex for about 3 weeks, but I wasn't all that impressed with their PVR features, since it is only in beta for now. So I started looking at Emby. Reviews were very good, so I decided to give it a try. I installed an Emby Server on a machine that has Windows 7 Professional, Intel Core i5 3.2Ghz, 4GB memory and a 1TB hard drive. Setup was pretty easy. I played with it for a couple of days and was so impressed that I signed up for Emby Premier so I could test the DVR and live TV. I added my tuners and used Schedules Direct (I already have an account with them for my Next PVR server) for my program listings. I played with the live tv on several devices, including Android tables, Android TV boxes and and Apple iPad. I also scheduled some recordings, both one time and series. Everything worked very well. So I stopped all my recordings on my Next PVR server and transfered them over to Emby. Everything looked to be going great! I had finally found the perfect PVR/Media Server! However, this weekend it all fell apart. I'm an avid Nascar fan, so I had set up a recording for the race this past Sunday. I also began watching the race live on my main TV, being broadcast on my local OTA station. My main TV has an Android TV box hooked up to it, so I used the Emby app to tune to my local station. The Emby app launches MX player to play the channel. All went well for about 30 minutes. Then the picture froze. Hmmm. Cheap Android box, I thought. So I rebooted it and went back into the Emby app, but it couldn't communicate with the server. So I go over to the server and it's SUPER SLOW, and the hard drive light is solid green. I hit CTRL-ALT-DEL and after about a minute the task manager was up and I see the Emby server is using almost 3.7GB! So the hard drive light being on was poor Windows trying to swap in virtual memory to take up the slack, which slowed the machine down to a crawl. So I rebooted the server. Back to normal. Server is using around 330MB. Restart the recording, restart the live TV. Same thing happens in about 20 minutes. Rebooted and tried it again. Same thing. Gave up and watched the race on my TV's tuner. So today I stick another 4GB of ram in the server, for a total of 8GB. That should make Emby happy, I thought. So I ran a test. I opened up a live TV channel (OTA, HD, 1080p) on my Android TV box. I looked at the memory usage of the server and it's around 350MB. So far so good. After a while I see the server's memory usage is going up. WAY UP. I watched it over a period of time, and after an hour the server usage was 7.5GB!! What is going on????? So I shut down the stream and watched the server's memory usage and it went down to 7.4GB and that's it. Of course, the server is dead slow right now. I assume the only way to get the memory usage back down is to reboot the Emby server. So, should I consider this normal???? What the heck is Emby doing with all that memory during a live stream? The CPU use during the stream is only about 4%, so the machine is not being strained at all. I certainly hope this is a bug, because if it isn't then Emby as a PVR is a bust, for me at least. I can't figure out why a live stream would cause the Emby server to require so much internal memory. Is it attempting to buffer the stream internally? I guess I was spoiled with Next PVR, it barely uses 150MB during it's operation. Using the current version of Emby (3.2.26.0). Thanks, Chuck

Hello all! I just had a quick question. Since using Emby (recovering Plex user here), I have noticed that memory usage steadily seems to increase even when it isn't streaming or engaging in scheduled tasks. IIRC, I often would get alerts via my alerting system regarding usage by the Emby process. That is when I began to the crontab to shutdown Emby via the API (step 1), then restart/daemonize (step 2) and write out the new PID so my monitoring system can pick it up (step 3). I am using Emby 3.2.8 with Mono 4.6.2.7 on Fedora 21. Is it feasible that memory use would perhaps plateau or has this been an issue with some users? Below is a screenshot of Emby memory usage over the past few days. The dips are the late night shutdowns, and as you can see usage steadily rises.

Recently Emby started crashing on my QNAP with 8 GB of RAM. I would restart it and it would run for a few hours and then stop suddenly. After taking a peek at the logs I can see that Emby ran out of memory indexing pictures. If I exclude the pictures from my Library then Emby indexes in about 2 minutes and stays up. If I include the pictures then indexing takes several hours and causes crashes. There are some new pictures but it seems to crash in some of the older folders. I love Emby and would not mind taking a go at trying to troubleshoot this further, but some questions before I do: 1. Would it be useful to troubleshoot this same symptom on a Linux/Windows VM? 2. Do we expect memory leaks or is there some confidence that it can't be a memory leak? 3. If there is no memory leak and we expect the problem is just too many pictures then is it worth trying the experimental x64 version? FWIW, the photo folder contains 850k files. But this includes the .nfo and other meta data that Emby creates. For 850k files to take 2GB of RAM would imply each file taking more than 2kB of RAM. Does that seem like something we expect?

Hello all, I'am running emby-server on an old netbook I had laying arround with an atom N450 processor and Ubuntu Server 14.04 32bit, as I have no need for transcoding atm it is perfect for my needs right now. Been running it for a couple of months as a backend for Kodi and working great. However, yesterday I upgraded the 1GB stick of RAM with a 2GB stick, the max the processor/mobo is capable. So because I upgraded the RAM I had a question, would I benefit from upgrading to a 64bit os, seeing as the processor is capable of it, but I was running 32bit ubuntu because of the low RAM. To find out, I decided to install a spare hard drive so I could install 32bit ubuntu, install emby-server, see cpu/ram consumption, then do the same with 64bit ubuntu and compare. However, as I was doing that with 32bit ubuntu I encountered something peculiar that I don't know if it's normal. I installed emby-server but haven't set up anything on the web ui just to see how the process acts with htop and discovered that after it starts it begins to consume more and more RAM till it's about 900MB, and then kinda restarts the process and begins doing it again. Because of that, I haven't tested 64bit ubuntu. So my question is, is that normal behavior for emby-server, maybe mono on linux, or maybe there's something wrong with my setup altought it's a fresh installation. I attached what I think it's the latest log at this moment, and I think it's showing an error but I don't really know. Thanks. Edit: What would you recommend, use 64bit ubuntu or stick with the 32bit? server-63593298069.txt

Emby seems to be running my Windows 10 PC out of memory ... Anyone else see this before... I'm using a Surface Pro to consume emby content when on the road ... I don't get this error with any other app.

Guys: I love MB. I've been a MB Classic user for years. Love the work you guys have done. I was happily using the latest 2.0 version and a friend encouraged me to upgrade to 3.0 which I did recently. On two different systems, one running Windows 7 with 8GB of RAM and one running Windows 8.1 with 16GB of RAM my system froze and the Media Browser Theater crashed with an error message stating that the system had insufficient memory to handle the task. I used MBC 2 to browse the same library for years without any such memory errors. This tells me that there is something unique going on in MB Theater while interacting with the MB Server that is causing this issue in the most recent release of MB. I've noticed a lot of other people have raised this issue of "memory crashes" in other parts of the forum. If someone in your development team could please kindly look into this matter in the context of the MB Theater and fix this bug, I would be very grateful and so would a lot of other people out there. I browsed through the same library with the MBC 2 version without any issues before. This is a unique MB 3.0 issue. Thank you for your assistance. Regards, Mike

Hi, I'm looking for a suggestion on building (or repurposing) a machine. Most of the ones that I've read have been general purpose machines for a lot of things. I'm really just looking for a machine that will be able to run MB3 server and transcode and stream up to a max of 8 different movies at the same time. There will be other programs running but minor ones. Is Windows 7 or Windows 8.1 preferred? Does it matter? Clients 2-3 MBT or MBC on Local LAN - Direct Play - No transcoding 2 - Local LAN Roku 3 - Local Wireless IOS 1 - Remote Roku 2 - Remote IOS I know these might not all be supported at this time but I want to take into account all of this for future overhead and not have to build again. Everything will be streamed from a NAS that is connected via gigabit ethernet. Mostly Movies and TV. Movies all 1080p source and TV is 720p source. My goal is not the break the bank but I'd like to get the best quality parts I can for the money right now as I'd rather not have to upgrade it in 2 years. Thanks for the help Josh

I've been running the latest beta for a while and memory hangs around 271.200 Megabytes. Not even sure how a 32-bit program can eat 6 GB of RAM. Could be a plugin though. I only have the Rotten Tomatoes and XBMC Metadata Plugins installed at this time. Windows 7 Premium, 8 GB Ram, Intel i5 2500K processor (quad-core).