Predator and CL could not provide any possible suspects.
Using the code search for the file, “optional.h” assigning to concern owner from GIT blame.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/c85bfab56bd24e8309d41d6accc888f952fd3cb2

@jdoerrie -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

I just reproduced this on Chrome OS (eve) on 69.0.3453.0 (developer build). I can pretty reliably get the crash by going to chrome://settings, finding a page with a drop-down <select> element, and selecting different options.

Reassigning to mlamouri@, who was the last person to touch media_control_overflow_menu_list_element.cc. The change is base::Optional is unrelated, and actually done to trigger more crashes in cases like this.

ClusterFuzz has detected this issue as fixed in range 579329:579330.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  storage_.is_populated_ in optional.h
  base::Optional<base::TimeTicks>::value
  blink::MediaControlOverflowMenuListElement::MaybeRecordTimeTaken
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=550784:550806
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=579329:579330

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

See https://github.com/google/clusterfuzz-tools 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 4830452482048000 is verified as fixed, so closing issue as verified.

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