How many items are in your library?
@primecut My stats as of a few months ago are in my signature at the bottom of this post.
Yeah, once an OOM exception has been thrown, it is going to get re-thrown by anything that attempts to grab another chunk of memory (while the condition still exists) and images are one of the things most likely to need memory.
However, if you look at your last log, the very first OOM that was thrown had nothing to do with images. It was attempting to do a recursive search of some part of your library related to doing an actual search via the API.
Knowing that your library is on the ridiculous side in terms of size (number of items) you may simply be hitting a physical limit with our current design and the fact we are a 32bit app. Have you tried using the hack that allows a 32bit app to run in a larger memory space?
@ebr I have used it in the past... I will certainly try it again But i monitor Emby it i never see it go above 1.2 gigs of ram.. even when these OOM errors happen i quickly check. What is the upper limit, i thought 2? Usually after it calms down it settles around 950 megs of ram usage. I used to get OOM errors when the app pushed the 2 gig mark... and the 4gig hack worked then.. but this seems to throw OOM errors at lower levels of ram usage and sometimes it crashes out, sometimes it pops an OOM window on my server. If i leave the window alone other OOM windows will pop up and the server keeps running.. some times it crashes out. Weird.. Ill try the hack first, but let me know what you think of the 1.2 gig usage.. I would actually like to see a 64 bit version.. EBR can you guys just apply the 4 gig hack out of the box, so we don't have to keep re-doing it on our end? Shouldn't affect 32bit users if i recall correctly that flag is ignored on a 32 bit machine is it?
As much as I hate to say it, @Luke and ebr are correct, about maintaining two versions, blah blah... I also understand you cant tend to the 1% (though I annoy the piss out of both of them every time I have an issue) If they jumped on every suggestion out there from every person eMBy would be a mess...
Maybe I should just use a linux VM and run eMBy within that?
I just tried the 4 gig patch and things seem somewhat stable, I'll wait and see when users start loading up the server.
Edited by pir8radio, 15 April 2015 - 08:14 PM.