Skip to content
  • Chaithra Gopalareddy's avatar
    9f50e36d
    Bug#16659166 - ASSERTION FAILED: 0, FILE GCALC_SLICESCAN.CC, LINE 743 · 9f50e36d
    Chaithra Gopalareddy authored
    Problem:
    Executing the query in the bugpage pegs CPU in optmized build and
    asserts in debug build
    
    Analysis:
    The function Gcalc_scan_iterator::pop_suitable_intersection()
    is expected to pass all the time. As a result while
    for debug build we have an assert for failure case, for optmized build
    it keeps looping as we dont check the return value of
    pop_suitable_intersection()
    
    Solution:
    We are avoiding the assert and also CPU utilization by checking the
    return value of the function
    9f50e36d
    Bug#16659166 - ASSERTION FAILED: 0, FILE GCALC_SLICESCAN.CC, LINE 743
    Chaithra Gopalareddy authored
    Problem:
    Executing the query in the bugpage pegs CPU in optmized build and
    asserts in debug build
    
    Analysis:
    The function Gcalc_scan_iterator::pop_suitable_intersection()
    is expected to pass all the time. As a result while
    for debug build we have an assert for failure case, for optmized build
    it keeps looping as we dont check the return value of
    pop_suitable_intersection()
    
    Solution:
    We are avoiding the assert and also CPU utilization by checking the
    return value of the function
Loading