Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

I think this is an assert statement crashing on bad input.

Agree. It's caused by LOG(FATAL). Marking this as Won't fix.

If you take a look at this fuzzer's stats: https://clusterfuzz.com/fuzzer-stats/by-day/date-start/2019-01-15/date-end/2019-01-21/fuzzer/libFuzzer_chromeos_imageloader_helper_process_receiver_fuzzer/job/libfuzzer_asan_chromeos

you can see that regular_crash_percent is 100% and fuzzing_time_percent is 0%, meaning that fuzzing is basically not happening because the fuzzer will crash immediately on every fuzzing run.

Unless that is fixed the fuzzer isn't really useful.

Do we have proper support for libprotobuf-mutator in chrome os? We plan to use this in imageloader so we can skip this type of crash. see crbug.com/904593

We have support, but I'm not what you mean by "proper" if you mean can it use protos that are optimized for the LITE_RUNTIME then I'm not sure. 
+allenwebb do you know the answer to this?

Sorry for my vague description. Yes, LITE_RUNTIME is what we need for imageloader (and some other system service protobufs).

libprotobuf-mutator will never support LITE_RUNTIME. What is in the works is getting the --cpp_out=speed:... feature included into Chrome OS with support for platform packages using GN to override the "option optimize_for = LITE_RUNTIME;" when building fuzzers. This is blocked by upreving protobuf which is blocked by a bug in the python eclasses.