Custom counters with ids from 0 to 31 silently fail with SlimTuneApi
GoogleCodeExporter opened this issue · 3 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Call WritePerfCounter with a counterId of any value within [0, 31]
2. Check at the generated graph in Performance Counters view
What is the expected output? What do you see instead?
I expect to see the data logged to counters 0 to 31 but they do not appear
at all, only counters with ids > 31 work. Counters with ids 1,2 and 3 do
not interfere with built-in Process: % processor time and such counters.
What version of the product are you using? On what operating system?
0.2.0, win7
Please provide any additional information below.
If that's intended behavior, documentation would be nice.
Original issue reported on code.google.com by tristanl...@gmail.com
on 17 Feb 2010 at 2:57
GoogleCodeExporter commented
This is intended behavior, and the plan is to call it out in docs for 0.2.1.
(0.2.0
does not have documentation, being a pre-release.)
Original comment by promit....@gmail.com
on 17 Feb 2010 at 3:04
- Changed state: WontFix
GoogleCodeExporter commented
In retrospect, silent fail was a dumbass idea. Will rebase the counter value
automatically instead.
Original comment by promit....@gmail.com
on 17 Feb 2010 at 3:20
- Changed state: Accepted
GoogleCodeExporter commented
This issue was closed by revision r162.
Original comment by promit....@gmail.com
on 17 Feb 2010 at 3:23
- Changed state: Fixed