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

Issue 747063 link

Starred by 2 users
Status: WontFix
Owner:
nzolghadr@chromium.org
Closed: Aug 2017
Cc:
tdres...@chromium.org
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !terminated_ in latency_info.cc

Project Member Reported by ClusterFuzz, Jul 20 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5660859618820096

Fuzzer: ipc_fuzzer_mut
Job Type: linux_asan_chrome_ipc
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !terminated_ in latency_info.cc
  ui::LatencyInfo::AddLatencyNumberWithTimestampImpl
  ui::LatencyInfo::AddLatencyNumber
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_ipc&range=488146:488166

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Jul 21 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-61
Owner: tdres...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "latency_info.cc" assigning to concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/7a5ff008cb7963c34c5207fa60145a1d7d9ea99a

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

Comment 2 by tdres...@chromium.org, Jul 21 2017

Cc: tdres...@chromium.org
Owner: nzolghadr@chromium.org
Navid, do you have bandwidth to take a look at this?
Project Member

Comment 3 by ClusterFuzz, Aug 20 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5660859618820096 is flaky and no longer reproduces, so closing issue.

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

Sign in to add a comment