Azure-functions-host: w3wp terminated due to unhandled exception

Created on 4 Aug 2016  路  4Comments  路  Source: Azure/azure-functions-host

I saw w3wp crashing with the exception below logged in eventlog.xml

I think it happens when I touch host.json while a bunch of queue functions are running.

Description: The process was terminated due to an unhandled exception.
Exception Info: System.ObjectDisposedException
   at System.Threading.CancellationTokenSource.ThrowObjectDisposedException()
   at System.Threading.CancellationTokenSource.InternalRegister(System.Action`1<System.Object>, System.Object, System.Threading.SynchronizationContext, System.Threading.ExecutionContext)
   at System.Threading.CancellationToken.Register(System.Action`1<System.Object>, System.Object, Boolean, Boolean)
   at System.Threading.CancellationToken.Register(System.Action)
   at Microsoft.Azure.WebJobs.Host.Timers.TaskSeriesTimer+<StopAsyncCore>d__4.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.Azure.WebJobs.Host.Queues.Listeners.QueueListener+<ProcessMessageAsync>d__11.MoveNext()
   at Microsoft.Azure.WebJobs.Host.Timers.BackgroundExceptionDispatcher+<>c__DisplayClass1.<Throw>b__0()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
bug

Most helpful comment

This was also a long time ago, if the info in the stack at the top are not meaningful, I'd just close this bug

All 4 comments

Actually now it seems to be happening without touching host.json

This might be tough since there is no clear repro. We might have some issues on our dispose paths.

This was also a long time ago, if the info in the stack at the top are not meaningful, I'd just close this bug

Agreed. Closing.

Was this page helpful?
0 / 5 - 0 ratings