navels 0 Posted November 10, 2016 Posted November 10, 2016 New owner of a DS215+ (1GB RAM, 2x2TB) with a recently installed Emby Server, migrated from my HTPC. Is the 1GB not enough? There is a particular that, as soon as I start playing it, crashes Emby with the below stacktrace. I can see in the Synology resource monitor that the RAM shoots up from 20% to 95% very quickly, then the crash. Thanks, Lee Out of memorySystem.OutOfMemoryExceptionat (wrapper managed-to-native) System.Object:__icall_wrapper_mono_array_new_specific (intptr,int)at System.IO.FileStream.InitBuffer (Int32 size, Boolean isZeroSize) <0x75007848 + 0x001c3> in <filename unknown>:0at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) <0x75005f40 + 0x0041f> in <filename unknown>:0at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize) <0x73f3a8e8 + 0x0005f> in <filename unknown>:0at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int)at CommonIO.ManagedFileSystem.GetFileStream (System.String path, FileMode mode, FileAccess access, FileShare share, Boolean isAsync) <0x6ecffe30 + 0x000df> in <filename unknown>:0at MediaBrowser.WebDashboard.Api.PackageCreator.GetRawResourceStream (System.String path) <0x70adb548 + 0x00067> in <filename unknown>:0at MediaBrowser.WebDashboard.Api.PackageCreator+<GetResource>d__6.MoveNext () <0x70adaac0 + 0x00207> in <filename unknown>:0--- End of stack trace from previous location where exception was thrown ---at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x6e316c08 + 0x00024> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x70ae91f8 + 0x000bb> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x70ae90b0 + 0x0008b> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x73057860 + 0x0003f> in <filename unknown>:0at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x72e319a8 + 0x0001b> in <filename unknown>:0at MediaBrowser.Server.Implementations.HttpServer.HttpResultFactory+<GetStaticResult>d__18.MoveNext () <0x70ad9398 + 0x006ef> in <filename unknown>:0--- End of stack trace from previous location where exception was thrown ---at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x6e316c08 + 0x00024> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x70ae91f8 + 0x000bb> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x70ae90b0 + 0x0008b> in <filename unknown>:0at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x73057860 + 0x0003f> in <filename unknown>:0at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x72e319a8 + 0x0001b> in <filename unknown>:0at MediaBrowser.Server.Implementations.HttpServer.HttpResultFactory+<GetStaticResult>d__15.MoveNext () <0x70af7770 + 0x004cb> in <filename unknown>:0--- End of stack trace from previous location where exception was thrown ---at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_array_new_specific (intptr,int)at System.IO.FileStream.InitBuffer (Int32 size, Boolean isZeroSize) <0x75007848 + 0x001c3> in <filename unknown>:0at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) <0x75005f40 + 0x0041f> in <filename unknown>:0at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize) <0x73f3a8e8 + 0x0005f> in <filename unknown>:0at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int)at NLog.Internal.FileAppenders.BaseFileAppender.TryCreateFileStream (Boolean allowFileSharedWriting) <0x73f3a350 + 0x001a7> in <filename unknown>:0at NLog.Internal.FileAppenders.BaseFileAppender.CreateFileStream (Boolean allowFileSharedWriting) <0x73f39960 + 0x00107> in <filename unknown>:0at NLog.Internal.FileAppenders.RetryingMultiProcessFileAppender.Write (System.Byte[] bytes) <0x73f397b8 + 0x00027> in <filename unknown>:0at NLog.Targets.FileTarget.WriteToFile (System.String fileName, NLog.LogEventInfo logEvent, System.Byte[] bytes, Boolean justData) <0x73f371c0 + 0x000a3> in <filename unknown>:0at NLog.Targets.FileTarget.ProcessLogEvent (NLog.LogEventInfo logEvent, System.String fileName, System.Byte[] bytesToWrite) <0x73f360e0 + 0x00163> in <filename unknown>:0at NLog.Targets.FileTarget.FlushCurrentFileWrites (System.String currentFileName, NLog.LogEventInfo firstLogEvent, System.IO.MemoryStream ms, System.Collections.Generic.List`1 pendingContinuations) <0x73f35918 + 0x00097> in <filename unknown>:0
Luke 42077 Posted November 10, 2016 Posted November 10, 2016 Hi, can you please attach the complete Emby server log? thanks !
solabc16 379 Posted November 10, 2016 Posted November 10, 2016 Hello @@navels The 1GB of memory your system has is more than sufficient, so that won't be the issue. As well as providing the complete log above for Luke, can you run the diagnostics and send logs utilities, which you can find details for on the Wiki here: https://github.com/M...elp-and-Support I just need the file reference you'll get when the send logs utility completes. Best - James
navels 0 Posted November 10, 2016 Author Posted November 10, 2016 Well I just tried playing the same movie on my HTPC's Emby (which is still up and running) and it quickly maxed out the RAM (16 GB, Win 10) and brought that box to its knees, so may be not worth diagnosing further in the context of the Synology app. I'll read some of the Windows OOM threads and ask for help over there if I need it. If there is still interest in getting the Synology diagnostics, though, let me know and I'll provide them. Thanks, Lee
navels 0 Posted November 10, 2016 Author Posted November 10, 2016 Hmmmm, turns out reproducing this problem on the the NAS is way easier than on my HTPC as the NAS fails faster and more gracefully (the app crashes) versus my HTPC which just becomes unresponsive and is awkward to recover. I just reproduced the crash (logs and diagnostics attached). Thanks! rundiags_20161110T173743UTC.log unhandled_ccbe6d75-65f7-45e8-b26f-6a9e47dcfc69.txt server-63614366480.txt
solabc16 379 Posted November 14, 2016 Posted November 14, 2016 Hello @@navels Are you able to run the send logs utility? (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs) - James
navels 0 Posted November 14, 2016 Author Posted November 14, 2016 (edited) Hello @@navels Are you able to run the send logs utility? (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs) - James I did but will do it again now. Hmmmm, this time I got: >> Creating archive... FAILED ERROR: Failed to create the log archive. Edited November 14, 2016 by navels
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