It seems that calling RenderAction() re-uses the filterContext for the MVC actionFilters, which results in a duplicate key exception.
If we need to track explicitly child-requests then maybe we should be using a stack for storing multiple stopwatches, but the simple approach is just to perform a .Contains() check.
It seems that calling
RenderAction()re-uses the filterContext for the MVC actionFilters, which results in a duplicate key exception.If we need to track explicitly child-requests then maybe we should be using a stack for storing multiple stopwatches, but the simple approach is just to perform a
.Contains()check.