search

beauli / slimtune

Automatically exported from code.google.com/p/slimtune
MIT License
0 stars 0 forks source link

The 3 default built-in performance counters show garbage data #27

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Profile using v0.2.0
2. Open the performance counters visualizer
3. Look at the "Process: % Processor Time", "Process: Private Bytes" and 
".NET CLR Memory: #GC Handles" counters

What is the expected output? What do you see instead?
All three counters show the exact same value which is some kind of 
oscillation between zero and negative values of a ridiculous magnitude. 
Here's a screenshot: http://yfrog.com/0sperfcounterj

What version of the product are you using? On what operating system?
0.2.0 backend, r168 UI, Win7

Please provide any additional information below.
If those counters are only supported in certain conditions, they should 
only appear if those are met.

Original issue reported on code.google.com by tristanl...@gmail.com on 21 Feb 2010 at 1:30

GoogleCodeExporter commented 8 years ago 
That...should not be happening. I'm not sure, I guess I'll keep an eye out for 
a repro.

Original comment by promit....@gmail.com on 21 Feb 2010 at 4:22

GoogleCodeExporter commented 8 years ago 
If you have specific things I can test, or functions I should debug locally, 
just tell 
me.

Original comment by tristanl...@gmail.com on 21 Feb 2010 at 2:02

GoogleCodeExporter commented 8 years ago 
Well the values in the Counters table shouldn't be negative (or even 
particularly
large), unless the original counter is reporting them that way. So the first 
thing to
do would be to verify that the graph is reporting the contents of the Counters 
table
correctly.

Beyond that, you'd have to see if the backend is really sending those bogus 
values,
which come from ClrProfiler::OnCounterTimer.

Original comment by promit....@gmail.com on 21 Feb 2010 at 6:55

GoogleCodeExporter commented 8 years ago 
Oh, and there's no fix for this issue incoming until after 0.2.1 is out.

Original comment by promit....@gmail.com on 21 Feb 2010 at 7:06

GoogleCodeExporter commented 8 years ago 
I've retooled the counters a bit to remove the crazy fixed point storage etc. 
Open a new issue if this shows up again.

Original comment by promit....@gmail.com on 16 Jul 2010 at 2:11