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

Issue 831442 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 15
Cc:
█ mkwst@chromium.org
dmazz...@chromium.org
█ brajkumar@chromium.org
pfeldman@chromium.org
aboxhall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Abrt in test_runner::WebAXObjectProxy::MisspellingsCount

Project Member Reported by ClusterFuzz, Apr 11 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6255702855909376

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  test_runner::WebAXObjectProxy::MisspellingsCount
  test_runner::WebAXObjectProxy::MisspellingAtIndex
  base::internal::Invoker<base::internal::BindState<std::__1::basic_string<char, s
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=535692:535694

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Apr 12 2018

Cc: dmazz...@chromium.org mkwst@chromium.org pfeldman@chromium.org brajkumar@chromium.org
Components: Blink
Labels: M-66 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no suspecting CL under regression range, hence adding appropriate label and cc'ing to few file owners as per  below link.
https://cs.chromium.org/chromium/src/content/shell/test_runner/OWNERS?sq=package:chromium&dr

Thanks!

Comment 2 by schenney@chromium.org, Apr 12 2018

Components: -Blink Blink>Accessibility
Project Member

Comment 3 by ClusterFuzz, May 17 2018

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6255702855909376 appears to be flaky, updating reproducibility label.
Project Member

Comment 4 by ClusterFuzz, May 17 2018

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 5 by ClusterFuzz, Jul 15

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 6255702855909376 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment