CHECK failure: mime_type == base::ToLowerASCII(mime_type) in plugin_list.cc |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4548519332151296 Fuzzer: attekett_surku_fuzzer Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: mime_type == base::ToLowerASCII(mime_type) in plugin_list.cc content::PluginList::GetPluginInfoArray content::PluginServiceImpl::GetPluginInfoArray Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4548519332151296 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Mar 22 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c1829894ac62e37257973d5e5c27d1bffb9888b3 (Remove remaining references to gconf). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Apr 5 2018
I feel very confident that my CL is not the culprit as the only code (not comments) that were changed were: - removing 2 unused files (and an unused build config) - changing some enums, mainly in mojo The enums that were changed don't even exist in the code base anymore. So it's not even possible to revert the change. The error is not actually reproducible locally either. Another potentially interesting note is that 4 bugs were assigned to me blaming this CL (this one, 820844, 817595, and one I've already unassigned myself from but can't find now). My suspicion is that a change in one of the DEPS is causing the problems, but I don't know how to confirm that.
,
Apr 13 2018
Unable to find actual suspect through code search and also observing no suspecting CL under regression range, hence adding appropriate label and requesting someone from internals team to look in to this issue. Thanks!
,
Aug 1
,
Oct 18
ClusterFuzz has detected this issue as fixed in range 600647:600648. Detailed report: https://clusterfuzz.com/testcase?key=4548519332151296 Fuzzer: attekett_surku_fuzzer Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: mime_type == base::ToLowerASCII(mime_type) in plugin_list.cc content::PluginList::GetPluginInfoArray content::PluginServiceImpl::GetPluginInfoArray Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905 Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=600647:600648 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4548519332151296 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.
,
Oct 18
ClusterFuzz testcase 4548519332151296 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Mar 22 2018Labels: Test-Predator-Auto-Components