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

Issue 726709 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
skyos...@chromium.org
█ brajkumar@chromium.org
█ msrchandra@chromium.org
altimin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CHECK failure: started in webthread_impl_for_worker_scheduler.cc

Project Member Reported by ClusterFuzz, May 26 2017 
Detailed report: https://clusterfuzz.com/testcase?key=6308764067299328

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  started in webthread_impl_for_worker_scheduler.cc
  blink::scheduler::WebThreadImplForWorkerScheduler::WebThreadImplForWorkerSchedul
  blink::scheduler::WebThreadBase::CreateWorkerThread
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=367545:367565

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

Comment 1 by msrchandra@chromium.org, May 26 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong M-59
Owner: skyos...@chromium.org
Status: Assigned (was: Untriaged)
Predator did not provide any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/73247c876566f0c49f140cb5eb72f2d2d6c8d8b2..15dfe4497acc9320e7453e38edec62acbf237716?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/57ad9a8b940ee57adbad24c0aa2cef7b5dcbbee9

@skyostil -- 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, May 26 2017

Labels: OS-Linux

Comment 3 by skyos...@chromium.org, May 26 2017

Cc: skyos...@chromium.org
Labels: -Pri-1 Pri-3
Owner: ----
Status: Available (was: Assigned)
This is an expected failure when we run out of OS resources. Keeping open so that other instances will be duped against this one.
Project Member

Comment 4 by ClusterFuzz, Aug 19 2017

Labels: OS-Android

Comment 5 by dtapu...@chromium.org, Aug 21 2017

Components: Blink>Scheduling

Comment 6 by altimin@chromium.org, Apr 3 2018

Status: WontFix (was: Available)
Marking as WontFix per comment #3 and the fact that there were no new bugs.
Project Member

Comment 7 by ClusterFuzz, Apr 10 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6308764067299328 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Comment 8 by brajkumar@chromium.org, Apr 24 2018

Cc: brajkumar@chromium.org
 Issue 835749  has been merged into this issue.

Comment 9 by kkaluri@chromium.org, Apr 30 2018 

Issue 837133 has been merged into this issue.
Project Member

Comment 10 by ClusterFuzz, Apr 30 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.
►

Sign in to add a comment