Bug #4836
closedprofiling: Invalid performance counter when using sampling
Description
Some signatures are returning a number of ticks that is out of this world when sampling rate is used:
@{
"checks": 1,
"gid": 1,
"matches": 0,
"percent": 49,
"rev": 10,
"signature_id": 2014702,
"ticks_avg": 94793124810508,
"ticks_avg_match": 0,
"ticks_avg_nomatch": 94793124810508,
"ticks_max": 94793124810508,
"ticks_total": 94793124810508
},
{
"checks": 1,
"gid": 1,
"matches": 0,
"percent": 0,
"rev": 10,
"signature_id": 2100327,
"ticks_avg": 6916,
"ticks_avg_match": 0,
"ticks_avg_nomatch": 6916,
"ticks_max": 6916,
"ticks_total": 6916
},@
Updated by Victor Julien about 3 years ago
- Status changed from New to Closed
- Target version changed from 6.0.5 to 7.0.0-beta1
- Affected Versions git master added
- Label Needs backport to 5.0, Needs backport to 6.0 added
Updated by Victor Julien about 3 years ago
- Subject changed from Invalid performance counter when using sampling to profiling: Invalid performance counter when using sampling
Updated by Jeff Lucovsky about 3 years ago
- Copied to Bug #4896: profiling: Invalid performance counter when using sampling added
Updated by Jeff Lucovsky about 3 years ago
- Copied to Bug #4897: profiling: Invalid performance counter when using sampling added