Call-Tree invisible

• 
  No, you should not have to wait longer. When the green wheel disappears, the call-tree should appear immediately.
  
  Does this bug occur every time? What type of application are you profiling?

  JasonC October 23, 2008 06:57

  - 0 +
• 
  Thanks, Jason
  
  I am profiling a Windows Forms 2.0 application (this one, to be precise).
  
  I did experience this behaviour this week for the first time, maybe it was present previously, too, but I did not recognize it.
  
  It does appear in 4.1, too, to which I upgraded today.

  Uwe Keim October 23, 2008 07:18

  - 0 +
• 
  I'm not really sure what could have caused this. It is probably a bug when profiling large applications with lots of results. We will try to repoduce it here at Red-Gate. Thanks for the information!

  JasonC October 23, 2008 08:28

  - 0 +
• 
  I'm using 1.0.1.9, but have been unable to get very far with it. When I try to open the standard example project, it says 'The standard project was not found'.
  
  When I try to create my own project it says 'Project created succesfully', but then gives me 'Object reference not set to an instance of an object', and doesn't open the project I just created.

  JasonC October 23, 2008 09:11

  - 0 +
• 
  Sorry for that, Jason!
  
  Do you use Windows Vista?
  You have an English (en-GB) system?

  Uwe Keim October 23, 2008 09:19

  - 0 +
• 
  I am using Windows XP. I have an en-GB system.

  JasonC October 23, 2008 09:24

  - 0 +
• 
  I'll immediately try to reproduce, please be patient.
  
  (and thanks for your support, I really appreciate!)

  Uwe Keim October 23, 2008 09:28

  - 0 +
• 
  Ah... I managed to fix it by copying the contents of the C:\Documents and Settings\jason.crease\My Documents\Zeta Test\Stationary\ENU directory to C:\Documents and Settings\jason.crease\My Documents\Zeta Test\Stationary\ENG.

  JasonC October 23, 2008 09:45

  - 0 +
• 
  Just found out, too after I set up a en-GB VMware machine.
  
  Will change my code immediately.

  Uwe Keim October 23, 2008 09:50

  - 0 +
• 
  Just updated the setup with the new version: http://zeta-test.com/preview.

  Uwe Keim October 23, 2008 10:37

  - 0 +
• 
  Awesome, using ZetaTest I've been able to repoduce both bugs you have reported. Thank you!
  
  Both are caused by the same issue. Your program has more complex stacktraces than most programs - largely due to use of XML and Regexes. Consequently, when ANTS Profiler tries to draw the call tree of your stack traces, it quickly runs out of memory.
  
  We will try to resolve this by trying improving the memory efficiency of ANTS Profiler. In the meantime, I can suggest the following:
  1. Profile in 'Only methods with source (fastest)' mode. This uses only a fraction of the memory used by other modes.
  2. Try using a x64 machine. Since ANTS Profiler will run as x64, there are no limits on its memory usage.

  JasonC October 23, 2008 10:46

  - 0 +
• 
  Thanks, Jason!
  
  Any suggestion on how to improve Zeta Test (which is currently Beta, of course) to lower the stack traces?
  
  Best regards
  Uwe

  Uwe Keim October 23, 2008 10:54

  - 0 +
• 
  Having lots of different stack traces isn't a bad thing - it is just often happens when using lots of XML and Regexes. I don't think this is a problem with Zeta Test, but just a problem with ANTS Profiler.
  
  To reduce the complexity of the Regex calls, it might be worth trying to use RegexOptions.Compiled, if you do not do so already. This will probably give you a speed increase, and reduce the complexity of stacktraces.

  JasonC October 23, 2008 11:16

  - 0 +

Add comment

Please sign in to leave a comment.