Adjustment to inotify?

[SkyBehind 23]

So I'm one of the folks that has trouble with inotify, if I have my libraries with realtime monitoring, it will crash every once in a while.  The below is a log from one of the events.  I also have a large library, would adjusting the watches limit help this (http://www.monodevelop.com/documentation/inotify-watches-limit/) 

 

 

 

 

 

System.NullReferenceException: Object reference not set to an instance of an object
at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <5641e4edad4f4464ba58c620a7b8ea48>:0
at System.IO.InotifyWatcher.Monitor () [0x0003c] in <5641e4edad4f4464ba58c620a7b8ea48>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
System.NullReferenceException
at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <5641e4edad4f4464ba58c620a7b8ea48>:0
at System.IO.InotifyWatcher.Monitor () [0x0003c] in <5641e4edad4f4464ba58c620a7b8ea48>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0

 

 

[Luke 37187]

Hi, I'm not sure, but considering that article is mentioning MonoDevelop it sounds pretty old. At this point the best workaround is simply to disable it.

 

We are trying to avoid new development based on mono and instead are focusing on switching to .net core:

https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core/

 

Nobody has reported a crash of this nature when running under .net core, so once our linux packages are switched over this should be a thing of the past. Thanks.

[SkyBehind 23]

Yeah, can't wait for .net core. I've thought about switching over to the Beta, but you know, Happy Wife = Happy Life and all.