Comments
Sort by recent activity
Not a problem.
I spoke to one of the developers about this and he thinks that deleting the DevExpress keys from the ANTS Profiler registry key would probably work.
We can't replicate this issue so no promises but if anyone else is reading this and has the same problem then please try it and let me know how you get on.
S / comments
Not a problem.
I spoke to one of the developers about this and he thinks that deleting the DevExpress keys from the ANTS Profiler registry key would probably work.
We can't replicate this issue so ...
Deleting everything in the Dock States key will fix the problem. It’s a DX bug as far as I can tell, haven't worked out a way we can fix it from within the profiler itself. / comments
Deleting everything in the Dock States key will fix the problem. It’s a DX bug as far as I can tell, haven't worked out a way we can fix it from within the profiler itself.
Just in case you haven't seen it there's also a Methods grid and a Call Graph feature - see the options bar underneath the call tree.
Now that the error has stopped - try the reset docking windows option again and then show source code view. Worth a punt. Apart from V5 i'm out of ideas.
We do have an early access program now for V6. Here's the forum where you can get the build. http://www.red-gate.com/messageboard/vi ... .php?f=110
It will install along side V5. I would imagine that the code view would be available when you install it. I just wouldn't go about closing it! [image]
Stephen / comments
Just in case you haven't seen it there's also a Methods grid and a Call Graph feature - see the options bar underneath the call tree.
Now that the error has stopped - try the reset docking windows ...
Happy to help.
Amongst other things we have planned for V6, the current build comes with the ability to analyze File I/O events and SQL events on a local instance of SQL Server if you are interested. There's a Sampling mode which is super quick if you don't need line level profiling.
You can 'switch' out the performance graph using the drop down in the top left corner and select the other graphs to do other analysis. If you have any colleagues etc... who would be interested then send on the link.
Any feedback on these features would be really appreciated.
Thanks,
Stephen / comments
Happy to help.
Amongst other things we have planned for V6, the current build comes with the ability to analyze File I/O events and SQL events on a local instance of SQL Server if you are intereste...
The profiler doesn't (or shouldn't) remember the state of the code window.
Closing down ANTS and then starting it back up again should automatically display the code window again no matter what its state in the previous profiling session.
If it's now never appearing between totally new sessions of having closed it down and started it up again that's a really strange bug. It appears to involve the 3rd party DevExpress control that's used for the window looking at the stack trace.
If it's the case that the code window doesn't show at all even when having restarted the profiler, then what happens when you start profiling and haven't yet displayed data of any type in the call tree for example - does clicking on the show source code option still then throw the exception with no profiling data visible?
I have one other possible solution to try but let me know how that goes first.
Stephen / comments
The profiler doesn't (or shouldn't) remember the state of the code window.
Closing down ANTS and then starting it back up again should automatically display the code window again no matter what its...
That's very strange.
So when you first started profiling and then got some data there was never a source code window there by default? Ever?
Because that's the state that is shown whenever the profiler is opened again for a totally new profiling session. Generally there shouldn't even be a real need to use that menu item really unless having manually closed the source code window which generally doesn't happen because the line level timings are generally of most interest.
It's very odd and any details you could provide would be helpful.
Stephen / comments
That's very strange.
So when you first started profiling and then got some data there was never a source code window there by default? Ever?
Because that's the state that is shown whenever the prof...
Hi,
just to quickly check - are you running the most recent version of ANTS Profiler?
Cheers,
Stephen / comments
Hi,
just to quickly check - are you running the most recent version of ANTS Profiler?
Cheers,
Stephen
Hi,
a couple of quick questions:
- which metric are you viewing your results in?
- does this appear to happen in other timing modes (method level, line level)
Stephen / comments
Hi,
a couple of quick questions:
- which metric are you viewing your results in?
- does this appear to happen in other timing modes (method level, line level)
Stephen
Switching to CPU time instead of Wall Clock time resolved this issue.
This is a reasonably common issue with people switching to one timing and not switching back to the other when it's more suitable for examining the results.
Timing: controls the way in which method timings are calculated. You can choose from Wall-clock time which includes blocking such as waiting for I/O, or CPU time which excludes any time blocking.
You can read more about the results the profiler shows you depending on what you select here: http://www.red-gate.com/supportcenter/Content.aspx?p=ANTS%20Performance%20Profiler&c=ANTS_Performance_Profiler/help/5.2/app_Working_with_the_call_tree.htm&toc=ANTS_Performance_Profiler/help/5.2/toc925914.htm
Regards,
Stephen / comments
Switching to CPU time instead of Wall Clock time resolved this issue.
This is a reasonably common issue with people switching to one timing and not switching back to the other when it's more suitab...
Hi Frank,
which version of the Profiler do you have?
Is it the Standard edition or the Pro edition?
Stephen / comments
Hi Frank,
which version of the Profiler do you have?
Is it the Standard edition or the Pro edition?
Stephen