SkyBehind 23 Posted January 23, 2017 Posted January 23, 2017 I've gotten this quite a few times over the past couple weeks and it causes the emby.service to stop. I'm on Ubuntu 16.04. This is the full log for Unhandled exception. Any ideas? System.NullReferenceException: Object reference not set to an instance of an objectat System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <bd46d4d4f7964dfa9beea098499ab597>:0at System.IO.InotifyWatcher.Monitor () [0x0003c] in <bd46d4d4f7964dfa9beea098499ab597>:0at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0System.NullReferenceExceptionat System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <bd46d4d4f7964dfa9beea098499ab597>:0at System.IO.InotifyWatcher.Monitor () [0x0003c] in <bd46d4d4f7964dfa9beea098499ab597>:0at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <8f2c484307284b51944a1a13a14c0266>:0at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
Luke 42077 Posted January 23, 2017 Posted January 23, 2017 Hi @@SkyBehind, try turning off the realtime monitor for libraries in which you have enabled it. Let us know if that helps. thanks !
SkyBehind 23 Posted January 23, 2017 Author Posted January 23, 2017 OK I turned it off for all libraries and will let you know. If I may ask, what made you think it was real time monitoring and which library is it (I have multiple libraries for TV because I have folders on a couple different drives for example).
Luke 42077 Posted January 23, 2017 Posted January 23, 2017 That particular exception is coming from the mono runtime and there's currently no way for us to catch it, so you either have to turn it off or live with the crashes. If the path is no longer valid then we've added a workaround for that situation for the next release.
SkyBehind 23 Posted January 25, 2017 Author Posted January 25, 2017 Just wanted to touch base... so far so good!
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