Build 242 feedback..

• 

  1/ Running build 242 I still do not get a summary displayed. Upon completion of the run I get the spinning circle saying that it is producing the summary. Today I left it running for 90 minutes whilst I went to a meeting and still didn't produce any summaries. I have yet to see a summary with version 4 and have runs from 20 seconds to 10 minutes.

  
  - The summary is just the stack trace view. There is a known bug where if you drag a region of code during profiling and then click the stop button or close your application it will keep saying summarising and this will be fixed in due course. Dragging out to select the entire timeline would give you the same result or alternatively not touching the timeline during profiling and then stopping your application would most likely work.
  

  2/ When it hangs as above I get the "index out of range error" reported by Lexicon.

  
  - Fixed in the next early access build which will be available shortly
  

  3/ When moving the mouse over my routines I get the message that "source code is available" when I double click on the routines I get "no source code available". This seems to be the same whatever mode I am in.

  
  - if source code for files aren't all in the same directory it won't be able to find it. A prompt will appear in future builds for you to locate where the source code for that file is.
  

  4/ The icons at the bottom left only the two on the very left "Call Tree" and "All methods grid" are enabled and do anything. Is this as expected?

  
  - Yes. Due to how early the build is some features haven't been implemented yet so they are greyed out.
  
  Thanks for your feedback,
  
  Stephen

  StephenC May 27, 2008 14:16

  - 0 +
• 
  Split into new topic..
  
  James

  James Moore May 27, 2008 16:00

  - 0 +
• 

  StephenC wrote:

  1/ Running build 242 I still do not get a summary displayed. Upon completion of the run I get the spinning circle saying that it is producing the summary. Today I left it running for 90 minutes whilst I went to a meeting and still didn't produce any summaries. I have yet to see a summary with version 4 and have runs from 20 seconds to 10 minutes.

  
  - The summary is just the stack trace view. There is a known bug where if you drag a region of code during profiling and then click the stop button or close your application it will keep saying summarising and this will be fixed in due course. Dragging out to select the entire timeline would give you the same result or alternatively not touching the timeline during profiling and then stopping your application would most likely work.
  

  
  FYI. I have run the profiler without touching the timeline and have tried both pressing the stop button and stopping the application and every time I run a trace the summary doesn't work.

  GrahamWade May 28, 2008 04:23

  - 0 +
• 
  That's strange. What is Task Manager showing as the CPU level for ANTS during the time it's summarising?
  
  I'm assuming it does, but with the very first time you load ANTS 4 (i.e. not having run any other sessions within the application), does it still happen?
  
  Does it happen with every application you have tried it on?
  
  We know of a bug when you go to start a new profiling session within ANTS as it hasn't all been implemented yet and it might do the same thing. However, if you aren't interacting with ANTS at all during the profiling and it's the first session we haven't heard of anything like that and haven't come across it ourselves.

  StephenC May 28, 2008 04:53

  - 0 +
• 

  StephenC wrote:

  That's strange. What is Task Manager showing as the CPU level for ANTS during the time it's summarising?

  
  Very little CPU activity (approx 1%) but I also looked at the program using Process Explorer and noticed that whilst it was "summarising" the following activity was occuring
  IO Other approx 20 per second
  Handles 700 -> 1200 -> 700 continuously approx 13 second cycle
  Context Switches : CorExeMain
  GetCLRFunction+0x1de53
  CreateManagedInstance+0x8aa4
  .NET CLR Security Runtime Checks climbing
  .NET CLR Interop # of marshalling climbing
  .NET Memory #GC Handles cycles 3000 -> 6000 -> 3000
  
  

  StephenC wrote:

  I'm assuming it does, but with the very first time you load ANTS 4 (i.e. not having run any other sessions within the application), does it still happen?

  
  Yes it happens every time.
  

  StephenC wrote:

  Does it happen with every application you have tried it on?

  It happens with all of my applications except one. The one where it does finish profiling it stated "no results" but selecting the timeline showed that there were results. Also I got the profiler to profile itself profiling one of my programs. The instance profiling my program didn't come out of "summarising" but when I closed that instance the one profiling the profiler worked as expected. :?
  

  StephenC wrote:

  We know of a bug when you go to start a new profiling session within ANTS as it hasn't all been implemented yet and it might do the same thing. However, if you aren't interacting with ANTS at all during the profiling and it's the first session we haven't heard of anything like that and haven't come across it ourselves.

  
  Hope some of this helps

  GrahamWade May 28, 2008 05:50

  - 0 +
• 
  Build 308 has been released Graham if you wish to try it out.
  
  It should fix a number of the larger bugs such as index out of range etc... as well as some of the summarising issues you mentioned.
  
  If you have the time to try it out and let me know if it has solved any of the issues you were experiencing that would be much appreciated.

  StephenC May 29, 2008 11:50

  - 0 +

Add comment

Please sign in to leave a comment.