Method EventWrite() and TimeLine profiling

I am using dotTrace TimeLine profiling to analyze a WPF application. According to the viewer, during most UI Freeze events the following method accounts for the largest proportion of own time in the call stack on the Main Thread:

                MS.Utility.ManifestTraceProvider.EventWrite(Event, Keyword, Level, Int32, EventData*)

Could this be a side-effect of the profiler itself?  In other words, if I were not running the timeline profiler, would this method consume as much resource?  In other words, can I exclude this method in my analysis?

1 comment
Comment actions Permalink
Official comment

Yes, it is a side-effect of the profiler, you can safely exclude this method from your analysis. We will fix this behavior in 2019.1 version of dotTrace.

Please sign in to leave a comment.