Call Count Way Too Large

I have section of code that I have tried to profile, but having trouble interpreting the results. When I run the application, there is one method call of interest inside a loop that iterates about twenty-some-odd times, but the call count when tracing is 242. Is this expected behavior? If so, how do I interpret this when the method is really only being called about a tenth of the time indicated? This just seems so basic that there must be something about what tracing is supposed to measure that I'm not understanding. Thx.



Never mind, figured it out. There are other calls to the same method, not in the loop in question, but elsewhere in the same routine, and it gloms them all together. Duh.


Please sign in to leave a comment.