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

Issue 823564 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
nhiroki@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Null-dereference READ in void base::internal::Invoker<base::internal::BindState<void

Project Member Reported by ClusterFuzz, Mar 20 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6236308067057664

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000068
Crash State:
  void base::internal::Invoker<base::internal::BindState<void
  blink::RunCrossThreadClosure
  base::internal::Invoker<base::internal::BindState<void
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=544053:544055

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 20 2018

Components: Internals>Core Platform
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.

Comment 2 by brajkumar@chromium.org, Mar 20 2018

Cc: nhiroki@chromium.org brajkumar@chromium.org
Labels: -Type-Bug M-67 Test-Predator-Wrong CF-NeedsTriage Type-Bug-Regression
Unable to find actual suspect through code search and also from the provided CL under regression range.

By comparing the stack trace this issue looks similar to  bug 791221 , hence cc'ing @nhiroki for more updates on this issue.

Thanks!
Project Member

Comment 3 by ClusterFuzz, Apr 3 2018

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 6236308067057664 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