You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exception: System.ObjectDisposedException EX59B6DA22
Message: The semaphore has been disposed.
StackTrace:
at System.Threading.SemaphoreSlim.CheckDispose()
at System.Threading.SemaphoreSlim.Release(Int32 releaseCount)
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.OutputReceivedHandler(String message, DisposeTrackingSemaphoreSlim semaphoreSlim)
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.\u003c\u003ec__DisplayClass49_0.\u003cCreateAndSetUpProcess\u003eb__1(String message)
at Jering.Javascript.NodeJS.NodeJSProcess.OutputThreadStart(Object arg)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
I see issue (152) mentions the fix was released in version 7.0.0. However, we encountered this error in production when we upgraded from 6.3.1 to 7.0.0.
The text was updated successfully, but these errors were encountered:
ahmedmansour-geotab
changed the title
The semaphore has been disposed
The semaphore has been disposed on release 7.0.0
Nov 22, 2023
ahmedmansour-geotab
changed the title
The semaphore has been disposed on release 7.0.0
The semaphore has been disposed Exception on release 7.0.0
Nov 22, 2023
ahmedmansour-geotab
changed the title
The semaphore has been disposed Exception on release 7.0.0
Exception: "The semaphore has been disposed" on release 7.0.0
Nov 22, 2023
NodeJs version: 16.13.2
Dotnet version: 7.0
Jering.Javascript.NodeJS package version: 7.0.0
Exception:
I see issue (152) mentions the fix was released in version 7.0.0. However, we encountered this error in production when we upgraded from 6.3.1 to 7.0.0.
The text was updated successfully, but these errors were encountered: