If a profile is terminated before the end time for a
method can be captured, JIP will create an artifical
end time that corresponds to the time that the profiler
itself was terminated. It is unusual for this to happen
but when it does, the profile is usually accurate.
However, there are some boundary cases where this
behavior will create artifically high method timings.
It would be nice to (optionally?) report to the user
that methods are being artifically "closed" and to
report which methods are impacted.
Log in to post a comment.