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

Issue 744560 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: result in icu_util.cc

Project Member Reported by ClusterFuzz, Jul 17 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6588342438461440

Fuzzer: ochang_domfuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result in icu_util.cc
  base::i18n::InitializeICU
  content::ContentMainRunnerImpl::Initialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487025:487028

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


Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-61
Owner: littledan@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "icu_util.cc" assigning to related owner who worked on similar file.

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

Comment 2 by ClusterFuzz, Jul 18 2017

ClusterFuzz has detected this issue as fixed in range 487028:487032.

Detailed report: https://clusterfuzz.com/testcase?key=6588342438461440

Fuzzer: ochang_domfuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result in icu_util.cc
  base::i18n::InitializeICU
  content::ContentMainRunnerImpl::Initialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487025:487028
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487028:487032

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


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 3 by ClusterFuzz, Jul 18 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: js...@chromium.org littledan@chromium.org machenb...@chromium.org
Owner: aga...@chromium.org
I don't know if this is an infrastructure issue or what, but I don't think it's from any of my changes. This bug keeps getting refiled and then closed by CF [1]. Assigning to agable with the hope that he'll be able to find the right owner for CF infra issues.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=738424
https://bugs.chromium.org/p/chromium/issues/detail?id=740052
https://bugs.chromium.org/p/chromium/issues/detail?id=741600
I don't think you'll be getting far by assigning verified bugs to people. Please file a new issue explaining the problem, possibly labelled with component:
Tools>Stability>Clusterfuzz and/or Infra

Comment 6 by aga...@chromium.org, Jul 18 2017

Yep, what machenbach said: a new bug in the Tools>Stability>Clusterfuzz component, pointing at this one and the others in your footnote, is the right way to go.

Sign in to add a comment