Redo the task but still this issue is not fixed. could someone please take a look?
Thank you.

I don't know what issue you are talking about. Can you please reference a bug. This is a totally new failure to me, and not part of any new code. I'm happy to look at this bug, but can you give me some more context.

I am talking about https://clusterfuzz.com/v2/testcase-detail/6123616648560640?noredirect=1
Yesterday we re-run the test and seems that not fixed.
Thank you.

This seems like a totally new bug to me. Can you point me to the CL that you thought fixed this. This in a part of code that has not been touched in a long time.

This issue is new and not fixed. sorry for the confusion. please take a look.
Thank you.

ClusterFuzz has detected this issue as fixed in range 467574:467606.

Detailed report: https://clusterfuzz.com/testcase?key=6123616648560640

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  RepeatX_RepeatY_pack_filter_x
  RepeatX_RepeatY_filter_scale
  BitmapProcShaderContext::shadeSpan
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=398502:398570
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=467574:467606

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6123616648560640


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6123616648560640 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.