You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second time will cause the array to be constructed, and m_singleBucketValue is populated into the array.
But within the third call, if (m_singleBucketNum == bucket) will still be true, and the metric is still added into m_singleBucketValue instead of the array.
Inside the indexer:
the m_singleBucketValue isn't used when the array is not null, causing the entry for m_singleBucketNum to be returned with incorrected value.
I don't have the whole knowledge of how Histogram is used, so I don't sure if this is really a bug. And this problem might not be a big issue due to the usage pattern, cause I don't see any bucket to be obviously wrong in the GUI.
The text was updated successfully, but these errors were encountered:
I was looking around the source code and the following piece of code seems a bit buggy to me:
perfview/src/TraceEvent/Stacks/Histogram.cs
Lines 48 to 68 in c671d46
Let's say the following sequence of
AddMetric
is called:The second time will cause the array to be constructed, and
m_singleBucketValue
is populated into the array.But within the third call,
if (m_singleBucketNum == bucket)
will still be true, and the metric is still added intom_singleBucketValue
instead of the array.Inside the indexer:
perfview/src/TraceEvent/Stacks/Histogram.cs
Lines 119 to 126 in c671d46
the
m_singleBucketValue
isn't used when the array is not null, causing the entry form_singleBucketNum
to be returned with incorrected value.I don't have the whole knowledge of how Histogram is used, so I don't sure if this is really a bug. And this problem might not be a big issue due to the usage pattern, cause I don't see any bucket to be obviously wrong in the GUI.
The text was updated successfully, but these errors were encountered: