Error when trying to clicking 'Show Source View'

[IBrown]

Hi,

I get the following error when clicking 'Show Source View' on a method. The method is shown in bold - so Performance Profiler believes that there is source to show. The code is in an IIS based ASP.net application.

Any suggestions? Thanks in advance.

The error message is:

[StephenC]

Hi,

just to quickly check - are you running the most recent version of ANTS Profiler?

Cheers,

Stephen

[IBrown]

I'm using the 14 day trial, labelled as 5.2.0.26.

Thanks for the quick reply.

[StephenC]

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

[IBrown]

To be honest - there may have been one there at some stage. I can't remember offhand. I've tried clicking 'Reset Docking Windows' but it doesn't seem to make any difference.

I don't know whether it helps, but I'm running XP, fully patched, with a dual monitor system.

[StephenC]

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

[IBrown]

Stephen,

OK - I've tried that. I still don't get the source window. However, when I click on the 'Show Source View' I now no longer get an error dialog - but nothing happens visually.

My screen shows the performance counters panel and the 'method' panel containing the tree view.

Incidentally, I am pretty impressed with the software as a whole.

[StephenC]

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/viewforum.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!

Stephen

[IBrown]

Stephen,

I'm downloading the EAP build of v6 and will try it later.

I have had a look at the methods grid and call graph - both look useful. The 'Reset Docking Windows' option did not have the desired effect.

Thanks for your help,

Ian.

[StephenC]

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

[IBrown]

Stephen,

I tried the eap of v6 - making sure that I didn't turn off the code view window. The code view window has reappeared in v5.2.

Thanks for your help.

[StephenC]

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

[SharedProphet]

[StephenC]

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.

[SharedProphet]