New issue
Advanced search Search tips

Issue 828352 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 806508
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in ui::X11EventSourceLibevent::X11EventSourceLibevent

Project Member Reported by ClusterFuzz, Apr 3 2018

Issue description

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

Fuzzer: inferno_twister_c
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  ui::X11EventSourceLibevent::X11EventSourceLibevent
  ui::OzonePlatform::InitializeForUI
  ui::Service::OnStart
  
Sanitizer: address (ASAN)

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

Additional requirements: Requires HTTP

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 3 2018

Components: Internals>MUS
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: kylec...@chromium.org
Components: -Internals>MUS Internals>Services>WindowService
Maybe fixed by recent ozone init changes?

Cc: -kylec...@chromium.org
Mergedinto: 806508
Owner: kylec...@chromium.org
Status: Duplicate (was: Untriaged)
This is essentially a duplicate of  issue 806508 . Same crash location with a slightly different stack. This was "fixed" by making it crash earlier if there is no X display which is the best we can do.

Sign in to add a comment