Similar to  issue 703510 ?. Predator and regression range did not given any suspected CL. 
alemate@, could you please take a look and duplicate if both are same.
Thanks for your help.

These two do not look the same. At least at the first glance.

Seems that same root cause of issue 705538 (but not 100% sure). msramek@, could you please take a look and help us to find correct owner if it is not related your changes.
Thank you in Advance.

I'm not sure what would point to the same root cause as issue 705538? It's a different regression range and a completely different stack trace.

The crash is in MessagePumpGLib. This might be related to the GTK change by this CL https://chromium.googlesource.com/chromium/src/+/072522801041708fba94498a1844cb89f24d4590 ?

thomasanderson@, could you please take a look?
Thank you.

ClusterFuzz has detected this issue as fixed in range 469308:469340.

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

Fuzzer: inferno_sampler
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000198
Crash State:
  g_main_context_dispatch
  g_main_context_iteration
  base::MessagePumpGlib::Run
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=455565:455674
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=469308:469340

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


Additional requirements: Requires Gestures

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 5297232086827008 is verified as fixed, so closing issue.

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