New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 824616 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Oct 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: mime_type == base::ToLowerASCII(mime_type) in plugin_list.cc

Project Member Reported by ClusterFuzz, Mar 22 2018

Issue description

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

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Mar 22 2018

Components: Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Mar 22 2018

Labels: Test-Predator-Auto-Owner
Owner: timbrown@chromium.org
Status: Assigned (was: Untriaged)
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.
Cc: timbrown@chromium.org
Labels: -OS-Linux Test-Predator-Wrong-CLs OS-Mac
Owner: ----
Status: Untriaged (was: Assigned)
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.
Cc: brajkumar@chromium.org
Labels: M-66 CF-NeedsTriage
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!
Labels: -OS-Mac OS-Linux
Project Member

Comment 6 by ClusterFuzz, 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.
Project Member

Comment 7 by ClusterFuzz, Oct 18

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
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