Comments
3 comments
-
Hi ncage,
This is a bug in APP, to do with how the profiler handles async code in vb.net. We're in the process of issuing a fix for it and there should be a new build available today or Monday.
The bug is PP-3163, for your reference. -
Thanks. I've updated the issue you created with the info you have asked of me. Can you give me the URL for your bug tracker where i can follow the bug?
thanks... -
For reference we've fixed this bug, and it should be available as a full release shortly.
Add comment
Please sign in to leave a comment.
The function i have highlighted its telling me it is taking 63.108 seconds. There is no way its even close to that. You can see how simple the function is. When i'm debugging, using visual studio 2015, that function takes less than a second. With all optimizations turned off. When i compiled my app for profiling with redgate of course i used a release build. If i switch it to CPU time instead of "Wall-clock time" the results are similar. Its telling me that 63.122 seconds of CPU time were taken.
To lessen profiler overhead i chose "method-level timings; methods with source"