User profile for Bart Read

Hi Cody, Sorry to see you're having problems. I can't reproduce this at all. I also checked an older version of Reflector and found that the functionality is the same. When you click on a node in the tree it is just selected whilst other panels, such as the disassembler, have their content updated. To drill down you need to click the +/- handles on the left hand side of the tree nodes (again, this is something that's always worked this way AFAIK). I'm not sure which "Expand Methods" link you're talking about; I can't find this. Can you perhaps post up a screenshot please? Thanks, Bart / comments

Hi Cody, Sorry to see you're having problems. I can't reproduce this at all. I also checked an older version of Reflector and found that the functionality is the same. When you click on a node in t...

0 votes

Thanks for getting in touch to let us know! Glad we were able to fix the problems you were having! / comments

Thanks for getting in touch to let us know! Glad we were able to fix the problems you were having!

0 votes

rgrenfell wrote: Do you know if the accept() routine is triggered as part of a socket.Poll() call? If so, what I was seeing would indeed be addressed by such a fix. If not, double check that the routines below Poll() are caught. No problem at all. Wish we'd spotted it sooner. With regard to the above, I'm honestly not sure, although you could use the find function to first find a call to Poll() and then to see if Accept() is called beneath that, which *should* give you the answer. You can also analyse Poll() in detail with the call graph: select the row and then click the little icon that appears to the right of the method name, or choose the option from the right-click menu. I'll also add an enhancement request for some more sophisticated filtering. Finally, I'll post here as soon as we have a build available that includes the fix. Thanks, Bart / comments

rgrenfell wrote: Do you know if the accept() routine is triggered as part of a socket.Poll() call? If so, what I was seeing would indeed be addressed by such a fix. If not, double check that t...

0 votes

Chaps, Sorry it's been a bit quiet on this topic lately. I'm expecting an ANTS Profiler 4.3 release to go out, fixing this problem, within the next 24 hours. I'll post an announcement once it's gone live. Thanks, Bart / comments

Chaps, Sorry it's been a bit quiet on this topic lately. I'm expecting an ANTS Profiler 4.3 release to go out, fixing this problem, within the next 24 hours. I'll post an announcement once it's gon...

0 votes

This should be fixed in the 4.3 release. To exclude all the blocking methods just select "CPU time" from the dropdown on the toolbar (it works now!). This should give you some much more relevant results. Download details are here: http://www.red-gate.com/messageboard/vi ... php?t=8569 Hope that helps, and sorry it's taken a while to get there. Thanks, Bart / comments

This should be fixed in the 4.3 release. To exclude all the blocking methods just select "CPU time" from the dropdown on the toolbar (it works now!). This should give you some much more relevant re...

0 votes

!!STOP PRESS!! There is a bug in our CPU/wall clock time support where, for some reason, the accept() method is not recognised as a blocking call. This will affect anyone profiling an ASP.NET application and probably the major reason you've been seeing problems. I've raised this as a matter of urgency, and it will be fixed in the 4.3 patch release, which will hopefully be available within the next couple of weeks. Ideally we'll have an early access build available including this fix within the next week. Apologies for the inconvenience. Many thanks, Bart / comments

!!STOP PRESS!! There is a bug in our CPU/wall clock time support where, for some reason, the accept() method is not recognised as a blocking call. This will affect anyone profiling an ASP.NET appli...

0 votes

Hi there Troy and rgrenfell, Sorry for the delay in replying to you. I'd meant to post a couple of days back. It is actually possible to filter by namespace in ANTS Profiler 4. What you need to do is switch to the methods grid, then click Tools > Find on the main menu, or just hit CTRL+F. Now just type your namespace name into the box. This also works for type and method names. You'll find the list should filter down as you type. You can also use the find functionality in the tree, although in this case it will drill down to the first matching node rather than filtering. On the topic of blocking time, make sure that on the toolbar below the tree/grid/graph you select "CPU time" rather than "Wall clock time" if you wish to exclude it. CPU time includes only time your application, or a particular thread within it spends executing on the CPU, whereas wall clock time also includes blocking time for I/O, sleeping, and suchlike. Note that methods which block can obviously also use quite a lot of CPU time for actual processing; I've seen SqlCommand.ExecuteReader() do this when executing a query that returns a large result set. I'd also recommend you only view methods with source in the tree and grid--again, you can change this on the toolbar underneath--and that you hide insignificant methods. Use the checkbox on the right hand side of this toolbar to control whether or not insignificant methods are shown--these are methods which take up less than 1% of the execution time for the selected period. If interesting processing is only happening on particular threads, I'd recommend you select the thread of interest from the threads drop-down. This means that if your blocking is occurring on another thread it'll be completely excluded from the results. Finally I'd echo Steve's comments about the timeline: use this as much as possible to only view data for the time period of interest. Just click and drag to select. If that doesn't help you out please let me know. Thanks, Bart / comments

Hi there Troy and rgrenfell, Sorry for the delay in replying to you. I'd meant to post a couple of days back. It is actually possible to filter by namespace in ANTS Profiler 4. What you need to do ...

0 votes

Hi there, It's almost certainly the garbage collection thread. You can verify that it's nothing to do with your code by using the threads drop-down (on toolbar beneath results tree view) to cycle through the results for your different threads. Hope that helps. Thanks, Bart / comments

Hi there, It's almost certainly the garbage collection thread. You can verify that it's nothing to do with your code by using the threads drop-down (on toolbar beneath results tree view) to cycle t...

0 votes

Hi Christoph, Thanks for reporting this. We are aware of the issue and in fact have recently fixed it in our latest dev branch. Normally I'd be more than happy to offer you a private build but we've made significant changes to the IIS support all of which, at present, are entirely untested. I should be in a position to offer you a build early in the New Year. Sorry I can't be of more immediate assistance. Thanks, Bart / comments

Hi Christoph, Thanks for reporting this. We are aware of the issue and in fact have recently fixed it in our latest dev branch. Normally I'd be more than happy to offer you a private build but we'v...

0 votes

Thanks Alex, There is also a workaround, in that you can just open a query with EXEC [ClassName].[TestSprocName] and set a breakpoint on that but it would be great to have something a bit more seamless. Cheers, / comments

Thanks Alex, There is also a workaround, in that you can just open a query withEXEC [ClassName].[TestSprocName] and set a breakpoint on that but it would be great to have something a bit more sea...

0 votes

How can we help you today?

Bart Read

Comments