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

Issue 622315 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Crash in blink::workerGlobalScopeDidError

Project Member Reported by ClusterFuzz, Jun 22 2016

Issue description

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

Fuzzer: therealholden_worker
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::workerGlobalScopeDidError
  WTF::PartBoundFunctionImpl<0,std::tuple<enum blink::UseCounter::Feature &&>,WTF:
  blink::internal::CallClosureTask<void __cdecl
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=401020:401085

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv9416-jJfqF6FAbX1MCX3QclL1DMww0zXV8AJrW7eUCMEo7L8x95V9W6XOy6azWovnAU2Z5E3o4GgVQkkMEaovRdcyx-lSwWDumCYy1nu6flllMFQNJ8Hu0qdqwrDy9kzfaIhZEx97P9HfNJJZrAaDZdsvmSFw?testcase_id=5535560471150592


Additional requirements: Requires HTTP

Filer: msrchandra

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Labels: -Type-Bug findit-wrong Te-Logged Type-Bug-Regression
Owner: dgozman@chromium.org
Status: Assigned (was: Available)
Below are the CL details,
https://chromium.googlesource.com/chromium/src/+log/b050f1526d5016e5e70d72682f4bb64b5ec2d50f..fef83f119f131fdaa01e19486b007fff506a41d4?pretty=fuller

Unable to find the owner using CL and find it.
Using Code Search for the file "workerwebsocketchannel.cpp", assigning it to concern owner.

Suspecting Commit# 49dc50ea2e6a95b9f5a84ab91dc7995e84f531c0
Suspecting Review URL# https://codereview.chromium.org/2004243002

@dgozman -- Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Jun 23 2016

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

Fuzzer: therealholden_worker
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::workerGlobalScopeDidError
  WTF::PartBoundFunctionImpl<0,std::tuple<blink::CrossThreadWeakPersistent<blink::
  blink::internal::CallClosureTask<void __cdecl
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=401477:401526

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv953PHYBPr32oqrgNfxaRJQoxESL-0VYj5BO60oKsJjkiq0fWw1mcqgQ1vQrqweqb2k_8yz5R6d2C1INoC8gKUmdB54zfUyWZ38bdf8GiSEK3wRdYD2RlKSqPuh0WvN5ouxkxiaAJn2erNbFLroLpkM0ftxoDg?testcase_id=6498661332942848


Additional requirements: Requires HTTP

Filer: mummareddy

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

Comment 3 by ClusterFuzz, Jun 28 2016

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: therealholden_worker
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::workerGlobalScopeDidError
  WTF::PartBoundFunctionImpl<0,std::tuple<blink::CrossThreadWeakPersistent<blink::
  blink::internal::CallClosureTask<void __cdecl
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=401477:401526

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv953PHYBPr32oqrgNfxaRJQoxESL-0VYj5BO60oKsJjkiq0fWw1mcqgQ1vQrqweqb2k_8yz5R6d2C1INoC8gKUmdB54zfUyWZ38bdf8GiSEK3wRdYD2RlKSqPuh0WvN5ouxkxiaAJn2erNbFLroLpkM0ftxoDg?testcase_id=6498661332942848


Additional requirements: Requires HTTP

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, Jul 5 2016

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: therealholden_worker
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::workerGlobalScopeDidError
  WTF::PartBoundFunctionImpl<0,std::tuple<enum blink::UseCounter::Feature &&>,WTF:
  blink::internal::CallClosureTask<void __cdecl
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=401020:401085

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv9416-jJfqF6FAbX1MCX3QclL1DMww0zXV8AJrW7eUCMEo7L8x95V9W6XOy6azWovnAU2Z5E3o4GgVQkkMEaovRdcyx-lSwWDumCYy1nu6flllMFQNJ8Hu0qdqwrDy9kzfaIhZEx97P9HfNJJZrAaDZdsvmSFw?testcase_id=5535560471150592


Additional requirements: Requires HTTP

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.
Components: Blink>Network>WebSockets
Labels: -ClusterFuzz Clusterfuzz
Owner: ----
Status: Untriaged (was: Assigned)
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: msrchandra@chromium.org
Status: Fixed (was: Untriaged)
As per Comment# 4, ClusterFuzz has detected the issue has been potentially fixed, so changing the status to Fixed. Pardon me if it has been wrongly marked.
Thank You.

Sign in to add a comment