Jump to content
Sign in to follow this  
jonnypajamas

trace calls found

8 posts in this topic Last Reply

Recommended Posts

Java keeps killing off processes as it is requiring more.  If you've got CrashPlan running, that'll be my primary guess as to the cause (its a pig)  After that, the next cause would be Plex

Share this post


Link to post

You could try limiting the memory available to your containers to say 4G (add this to all of them).  Also, don't have Plex transcode to RAM.  Plex is my guess, but realistically you have to figure out what was going on at the time of the OOM errors.  All containers will use whatever is available to them.  Things like D/L clients will use all available RAM if they can when unpacking, and if something else needed the memory at the same time, then you're SOL.  

 

That, and you could always upgrade your RAM

 

 

Share this post


Link to post

i have plex set to transcode to an unassigned ssd.  My subsonic failed on me, it may have been that which was throwing errors.

Share this post


Link to post
6 minutes ago, jonnypajamas said:

i have plex set to transcode to an unassigned ssd.  My subsonic failed on me, it may have been that which was throwing errors.

Its a play thing.  All we know is that whatever app is running that uses Java triggered the error.  But, it may not have actually been the guilty party.  It could be something else.  (Guilty by association?)

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this