Predator and CL could not provide any possible suspects.

Using the code search for the file, “command_line.cc” assigning to concern owner.
Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/a16212a56df0ed74f3f1e3029563e57d53f8c031

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


Thank You...

This should go to the owner of content::AreExperimentalFeaturesEnabled

Or possibly the caller of that. It looks like something is calling things that want a command line when there is not one set up for the process.

ClusterFuzz has detected this issue as fixed in range 517415:517454.

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

Fuzzer: libFuzzer_clear_site_data_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  current_process_commandline_ in command_line.cc
  base::CommandLine::ForCurrentProcess
  content::AreExperimentalFeaturesEnabled
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=517035:517051
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=517415:517454

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5705434639106048 is verified as fixed, so closing issue as verified.

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