New issue
Advanced search Search tips

Issue 828170 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in base::internal::Invoker<base::internal::BindState<content::GpuProcessHost::InitO

Project Member Reported by ClusterFuzz, Apr 2 2018

Issue description

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

Fuzzer: ochang_search_index_mutator
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  base::internal::Invoker<base::internal::BindState<content::GpuProcessHost::InitO
  base::internal::Invoker<base::internal::BindState<content::OzoneRegisterStartupC
  ui::OzonePlatform::RegisterStartupCallback
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Apr 2 2018

Components: Internals>GPU>Internals
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.
Cc: dnicoara@chromium.org
Owner: rjkroege@chromium.org
Status: Assigned (was: Untriaged)
Ozone init issue it seems. rjkroege@, can you decide how to prioritize this?
Owner: sadrul@chromium.org
sadrul@ can you look?

Comment 4 by sadrul@chromium.org, Apr 16 2018

Cc: kylec...@chromium.org
crrev.com/549523 probably fixed this?
Project Member

Comment 5 by ClusterFuzz, Apr 20 2018

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
sadrul: I guess so.

Sign in to add a comment