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

Issue 684456 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Crash in content::ActionsParser::ParsePointerActionSequence

Project Member Reported by ClusterFuzz, Jan 24 2017

Issue description

Cc: msrchandra@chromium.org
Components: Internals>Core
Labels: Test-Predator-Wrong-CLs
Owner: lanwei@chromium.org
Status: Assigned (was: Untriaged)
Find it and CL did not find any possible suspects.
Using Code Search for the file, "actions_parser.cc" assigning to the concern owner.

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

@lanwei -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by lanwei@chromium.org, Jan 24 2017

Sure, I will take a look. Could you please tell how to reproduce the crash locally, thank you?
Project Member

Comment 3 by ClusterFuzz, Jan 31 2017

ClusterFuzz has detected this issue as fixed in range 446721:447186.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5436941593214976

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  content::ActionsParser::ParsePointerActionSequence
  content::GpuBenchmarking::PointerActionSequence
  gin::internal::Dispatcher<bool
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=445235:445259
Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=446721:447186

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94oEn7KUr1BENoReK7E7odwbQszHBhAvFzvKHN-KS2ES8q1mTCifhSHG2zLQKTpP-x14pbdDxg6O3FQxx0qRJDcbdelY1T7R0uam-ZFnxp6VnCGujNV_2JxprAYvCHD8zGEZqXGl5oIur9gUJc4zyfB6Z6d3-28mmEfweJVIAcW3lM1Zc3Cx7AZLYk4CiJ7Av2hCx4LFuFIxwsKxgbIWTemZL0hPy5JJjL_bQdObTjtcnK59BbyS9ybkvnwgYRbCYCv4A-1E4wMdlhmHkpMNeukxi6HW83rGG_j16SNkJ-tuzgUGzrpeW54Ki488Hyp4H73dV7aE6BG_I4jjwrsPpKdv6EZgCCPprWCum7-e_MNd_YaaDVkfylKDXRWX3cU0QaCOxix2gZljG3-LsQ7W9gdU0TbQQ?testcase_id=5436941593214976


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 4 by ClusterFuzz, Jan 31 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5436941593214976 is verified as fixed, so closing issue.

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

Sign in to add a comment