Jump to content

Emby OUT OF MEMORY ERRORS


pir8radio
Go to solution Solved by pir8radio,

Recommended Posts

jabbera

Some (old) unmanaged code would use the top bit of a 32 bit pointer to actually maintain some program state about the points to object. I've never ran into one of these. I would be shocked if there was any side effect of making Emby large address aware.

Link to comment
Share on other sites

pir8radio

@@ebr an update, my server has been running flawlessly since the 4gb "hack"....      If that is something that can get worked into the releases/updates that would be great...  I think that will allow you guys to get way more life out of the 32bit version. 

Link to comment
Share on other sites

mediacowboy

I am seeing a bunch of these. Attached are my log's. I am running Emby server 3.0.5588.1. These logs are from 4/23/2015 4:34PM to 8:51 PM.

Error.zip

Link to comment
Share on other sites

AgileHumor

well i don't think there's any reason to impose an artificial limitations on linux just because of windows. if you want to help do the work for 64-bit then yes it can be done.

You are imposing a limit for 64 bit users (large majority of new Emby installs) unless you change the compiling process (which will still work for 32 bit and 64 bit systems):

http://stackoverflow.com/questions/570589/can-a-32bit-process-access-more-memory-on-a-64bit-windows-os 

 

 

Have you tried using the hack that allows a 32bit app to run in a larger memory space?

 

The 3GB hack only works on 32 bit systems needing to address larger then 2GB of app ram...doesn't work in 64 bit OS (~90% of new Emby installs)

 

I have not tested this utility, but it might help fix the compiler flag in the App without the Dev team making changes.

http://www.maketecheasier.com/increase-memory-limit-for-32-bit-applications-in-windows-64-bit-os/

 

 

PS - Amazing that 32 bit because "codecs" are easier to install (which is not my experience in 2015, maybe 2005)...the platform is limited for large libraries. 

Edited by AgileHumor
Link to comment
Share on other sites

saitoh183

The 3GB hack only works on 32 bit systems needing to adress larger then 2GB of app ram...doesn't work in 64 bit OS (~90% of new Emby installs)

 

I have not tested this utility, but it might help fix the compiler flag in the App without the Dev team making changes.

http://www.maketecheasier.com/increase-memory-limit-for-32-bit-applications-in-windows-64-bit-os/

 

 

For the people that were having problems, that was what we were already using and is also what we are discussing in this thread

Link to comment
Share on other sites

AgileHumor

dead link

 

Link is correct, the forum added a white space at end which their sever can't accept.  I tried again without whitespace...but if that doesn't work...just delete the extra character to view the page on TechRepub weird web server. 

 

http://www.techrepublic.com/blog/windows-and-office/override-the-4gb-memory-barrier-on-32-bit-windows-81-systems/

Edited by AgileHumor
Link to comment
Share on other sites

AgileHumor

For the people that were having problems, that was what we were already using and is also what we are discussing in this thread

 

 

Sorry, I missed pirates post of the links.    Got super anxious that months of server instability could be attributed to such a simple fix while reading the threads from #1....scanned to much at the end.   Was also shocked that large library stability issues we're specifically being skipped.  Wish I knew that before posting logs over many months to have it ignored.   Now that I know, it saves us all time from reading or posting. 

Edited by AgileHumor
Link to comment
Share on other sites

AgileHumor

Where are you getting that metric?

Google, eyes, ears.

 

http://store.steampowered.com/hwsurvey  (click OS Versions in left column of table) shows 79%

 

Windows 7 64 bit 46.67%-0.05%
Windows 8.1 64 bit 28.73%+1.10%
Windows 7 10.52%-0.35%
Windows XP 32 bit 3.64%-0.09%
Windows 8 64 bit 3.44%-0.32%
Windows 10 64 bit 0.70%+0.48%
Windows 8.10.63 %0.00%
Windows Vista 32 bit 0.51%-0.07%
Windows Vista 64 bit 0.28%-0.77%

 

Reference: http://community.spiceworks.com/topic/426628-windows-32-bit-vs-64-bit-market-share 

Link to comment
Share on other sites

But how does that relate to Emby users?  That's my point.  I don't actually know what the metrics are for 32 vs 64 because we don't track it but I do know that over half of the Emby servers out there are running on Win 7 - which means they aren't going onto brand new installs of brand new OSes.

 

No one is ignoring anything.  We simply have to prioritize.  

Link to comment
Share on other sites

saitoh183

The bottom line is that if there is a way to accommodate 64bit in the current emby package,that is what would be ideal. As for most running on Windows 7, that doesn't mean they are mostly on 32 bit either.

Link to comment
Share on other sites

The bottom line is that if there is a way to accommodate 64bit in the current emby package,that is what would be ideal. As for most running on Windows 7, that doesn't mean they are mostly on 32 bit either.

 

No, like I said, we really don't know.  So we can't say that 90% of new Emby users are on x64.

Link to comment
Share on other sites

mediacowboy

Ok,now that we have that figured out can someone look at my logs and tell me what I need to do to fix my errors. Besides using a "hack" since this just started.

Link to comment
Share on other sites

techywarrior

No, like I said, we really don't know.  So we can't say that 90% of new Emby users are on x64.

Perhaps you could add that to the metrics you get? Or a simple poll to get a general idea?

 

I think you will find that most are actually on x64. The places you may find 64bit to be a problem is on the embedded devices (qnap, synology, unRAID, etc.). A lot of those OSes are probably 32bit since they don't have a lot of need to be 64bit.

 

Linux, Windows, OS X are going to be predominantly 64bit. I would hazard a guess that 99% of the Linux installs on server/desktop are 64bit and 100% OS X should be. Windows I would expect to be 90%+ for the machines running Emby server since MS has been pushing 64 bit heavily starting with Win7 (partially with Vista, and a token effort with XP).

  • Like 4
Link to comment
Share on other sites

CashMoney

One thing to keep in mind that may skew your mainly 64bit OS install idea. How many Emby users came from MB2? And more importantly how many are still using the same hardware? I run 64bit exclusively on everything .... except my Emby server which is just simply upgraded from my MB2 HTPC and is still on 32bit because it's an old Celeron dual core :)

 

Of course I could be just impressing my own experience into my opinion (as could others :) ) but going forward I will eventually upgrade my server HTPC to take better advantage of the sync features and HD transcoding, at which point I'll be adding of ram and of course going 64bit.

Link to comment
Share on other sites

techywarrior

Well, without automated metrics we won't know for sure but I considered your case when I said 90%. Since every Intel chip for the last 10 years has been 64 bit there is a good chance that people would have installed 64bit OS (assuming Win7+). Obviously not always the case but the other nice thing is that if you happen to have used Win7 retail then you already should have both 32bit and 64 bit so you could reinstall if you like. Of course OEM install media was only one or the other depending on what you purchased.

  • Like 1
Link to comment
Share on other sites

pir8radio

Well i don't know how many other users are getting the OOM errors for legit reasons...  I believe my reason was Emby maybe caching that many items (either titles, names, images or whatever) this hack worked for me..

 

Someone said this "hack" is for 32 bit users only that it doesn't work on 64 bit.. That is incorrect. It specifically addresses 32bit applications running on a windows 64bit machine.  I know it works because i have seen my memory usage (in some older MB versions) push 2.5 to 2.7 gigs of ram, here is a snapshot in my old post with picture proof:  http://emby.media/community/index.php?/topic/12014-large-library-causing-issues/

 

All i know is the 4 GB ram hack worked for me, Emby has been rock solid!  Its still open to guests + my regular users... I have 3 people watching HD movies right now, i haven't had to reboot since the hack.  I personally would love to see the "hack" which it is NOT, built into emby..   This "hack" is a windows supported flag to allow the app to use larger address space.

Link to comment
Share on other sites

Happy2Play

The only way I have been able to get my server to produce an OOM error was to nuke my server cache and use the server while it was rebuilding.

Link to comment
Share on other sites

pir8radio

The only way I have been able to get my server to produce an OOM error was to nuke my server cache and use the server while it was rebuilding.

 

Here is what my Emby server uses while idle, FYI

 

553af1db570d8_Server2.png

Link to comment
Share on other sites

Happy2Play

Here is mine, currently rebuilding cache.

553af3d514dad_Memory.jpg

Edited by Happy2Play
Link to comment
Share on other sites

MrWebsmith

does this need to be re-run after updates to the exe? or its a "hack it and forget it" ;) ??

Link to comment
Share on other sites

AgileHumor

Yes, every update will need the patch until the development team sets the compiler flag correctly.

 

PS - No OOM errors for 3 days.  That is a record since the server started crashing daily for multiple bugs over the last month.  

  • Like 2
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...